From 6778948f9de86c3cfaf36725a7c87dcff9ba247f Mon Sep 17 00:00:00 2001
From: hc <hc@nodka.com>
Date: Mon, 11 Dec 2023 08:20:59 +0000
Subject: [PATCH] kernel_5.10 no rt
---
kernel/Documentation/driver-api/firmware/request_firmware.rst | 7 ++++++-
1 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/kernel/Documentation/driver-api/firmware/request_firmware.rst b/kernel/Documentation/driver-api/firmware/request_firmware.rst
index f62bdcb..0d6ea03 100644
--- a/kernel/Documentation/driver-api/firmware/request_firmware.rst
+++ b/kernel/Documentation/driver-api/firmware/request_firmware.rst
@@ -25,6 +25,11 @@
.. kernel-doc:: drivers/base/firmware_loader/main.c
:functions: firmware_request_nowarn
+firmware_request_platform
+-------------------------
+.. kernel-doc:: drivers/base/firmware_loader/main.c
+ :functions: firmware_request_platform
+
request_firmware_direct
-----------------------
.. kernel-doc:: drivers/base/firmware_loader/main.c
@@ -71,5 +76,5 @@
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.
--
Gitblit v1.6.2