Re: [PATCH 1/5] drm/i915/dmc: handle request_firmware() errors separately

2024-04-18 Thread Gustavo Sousa
Quoting Jani Nikula (2024-04-18 16:56:06-03:00) >On Thu, 18 Apr 2024, Gustavo Sousa wrote: >> Quoting Jani Nikula (2024-04-18 11:39:50-03:00) >>>Clarify request_firmware() error handling. Don't proceed to trying to >>>parse non-existent firmware or check for payload when request_firmware()

Re: [PATCH 1/5] drm/i915/dmc: handle request_firmware() errors separately

2024-04-18 Thread Jani Nikula
On Thu, 18 Apr 2024, Gustavo Sousa wrote: > Quoting Jani Nikula (2024-04-18 11:39:50-03:00) >>Clarify request_firmware() error handling. Don't proceed to trying to >>parse non-existent firmware or check for payload when request_firmware() >>failed to begin with. There's no reason to

Re: [PATCH 1/5] drm/i915/dmc: handle request_firmware() errors separately

2024-04-18 Thread Gustavo Sousa
Quoting Jani Nikula (2024-04-18 11:39:50-03:00) >Clarify request_firmware() error handling. Don't proceed to trying to >parse non-existent firmware or check for payload when request_firmware() >failed to begin with. There's no reason to release_firmware() either >when request_firmware() failed. >

[PATCH 1/5] drm/i915/dmc: handle request_firmware() errors separately

2024-04-18 Thread Jani Nikula
Clarify request_firmware() error handling. Don't proceed to trying to parse non-existent firmware or check for payload when request_firmware() failed to begin with. There's no reason to release_firmware() either when request_firmware() failed. Also move the message about DMC firmware homepage