aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/driver-api/firmware/direct-fs-lookup.rst
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/driver-api/firmware/direct-fs-lookup.rst')
-rw-r--r--Documentation/driver-api/firmware/direct-fs-lookup.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/driver-api/firmware/direct-fs-lookup.rst b/Documentation/driver-api/firmware/direct-fs-lookup.rst
index 82b4d585a213..e04353d1b06b 100644
--- a/Documentation/driver-api/firmware/direct-fs-lookup.rst
+++ b/Documentation/driver-api/firmware/direct-fs-lookup.rst
@@ -24,7 +24,7 @@ available. Stuffing the firmware into initramfs resolves this race issue,
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.