lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri,  3 Jul 2020 20:44:50 -0700
From:   Randy Dunlap <>
Cc:     Randy Dunlap <>,
        Jonathan Corbet <>,,
        Vinod Koul <>,,
        Luis Chamberlain <>,
        Greg Kroah-Hartman <>,
        William Breathitt Gray <>,,
        Mauro Carvalho Chehab <>,, Jon Mason <>,
        Dave Jiang <>,
        Allen Hubbe <>,,
        Dan Williams <>,
        Vishal Verma <>,
        Ira Weiny <>,,, Eli Billauer <>
Subject: [PATCH 05/17] Documentation/driver-api: firmware/request_firmware: drop doubled word

Drop the doubled word "call".

Signed-off-by: Randy Dunlap <>
Cc: Jonathan Corbet <>
Cc: Luis Chamberlain <>
Cc: Greg Kroah-Hartman <>
 Documentation/driver-api/firmware/request_firmware.rst |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- linux-next-20200701.orig/Documentation/driver-api/firmware/request_firmware.rst
+++ linux-next-20200701/Documentation/driver-api/firmware/request_firmware.rst
@@ -76,5 +76,5 @@ firmware. For example if you used reques
 the driver has the firmware image accessible in fw_entry->{data,size}.
 If something went wrong request_firmware() returns non-zero and fw_entry
 is set to NULL. Once your driver is done with processing the firmware it
-can call call release_firmware(fw_entry) to release the firmware image
+can call release_firmware(fw_entry) to release the firmware image
 and any related resource.

Powered by blists - more mailing lists