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:49 -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 04/17] Documentation/driver-api: firmware/direct-fs-lookup: drop doubled word

Drop the doubled word "firmware".

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

--- linux-next-20200701.orig/Documentation/driver-api/firmware/direct-fs-lookup.rst
+++ linux-next-20200701/Documentation/driver-api/firmware/direct-fs-lookup.rst
@@ -24,7 +24,7 @@ available. Stuffing the firmware into in
 however note that using initrd does not suffice to address the same race.
 There are circumstances that justify not wanting to include firmware into
-initramfs, such as dealing with large firmware firmware files for the
+initramfs, such as dealing with large firmware files for the
 remote-proc subsystem. For such cases using a userspace fallback mechanism
 is currently the only viable solution as only userspace can know for sure
 when the real rootfs is ready and mounted.

Powered by blists - more mailing lists