firmware: improve description of firmware_request_nowarn
The doubled 'however' is confusing. Simplify the comment a little and reformat the paragraph. Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com> Acked-by: Luis Chamberlain <mcgrof@kernel.org> Link: https://lore.kernel.org/r/20200702221107.6562-1-wsa+renesas@sang-engineering.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:

committed by
Greg Kroah-Hartman

parent
cad064f1bd
commit
2fce60be06
@@ -838,12 +838,12 @@ EXPORT_SYMBOL(request_firmware);
|
|||||||
* @name: name of firmware file
|
* @name: name of firmware file
|
||||||
* @device: device for which firmware is being loaded
|
* @device: device for which firmware is being loaded
|
||||||
*
|
*
|
||||||
* This function is similar in behaviour to request_firmware(), except
|
* This function is similar in behaviour to request_firmware(), except it
|
||||||
* it doesn't produce warning messages when the file is not found.
|
* doesn't produce warning messages when the file is not found. The sysfs
|
||||||
* The sysfs fallback mechanism is enabled if direct filesystem lookup fails,
|
* fallback mechanism is enabled if direct filesystem lookup fails. However,
|
||||||
* however, however failures to find the firmware file with it are still
|
* failures to find the firmware file with it are still suppressed. It is
|
||||||
* suppressed. It is therefore up to the driver to check for the return value
|
* therefore up to the driver to check for the return value of this call and to
|
||||||
* of this call and to decide when to inform the users of errors.
|
* decide when to inform the users of errors.
|
||||||
**/
|
**/
|
||||||
int firmware_request_nowarn(const struct firmware **firmware, const char *name,
|
int firmware_request_nowarn(const struct firmware **firmware, const char *name,
|
||||||
struct device *device)
|
struct device *device)
|
||||||
|
Reference in New Issue
Block a user