summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRandy Dunlap <rdunlap@infradead.org>2020-07-03 20:44:50 -0700
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2020-07-10 14:58:01 +0200
commit726b5bd3cf9705f1beea872c093ecdcc2376d477 (patch)
tree3218691b7a579cc6053225b994682d270f11c4ad
parente2e4e8f5ac69ab8b50c00243172d79ee67aa6b69 (diff)
downloadlinux-726b5bd3cf9705f1beea872c093ecdcc2376d477.tar.bz2
Documentation/driver-api: firmware/request_firmware: drop doubled word
Drop the doubled word "call". Signed-off-by: Randy Dunlap <rdunlap@infradead.org> Cc: Jonathan Corbet <corbet@lwn.net> Cc: linux-doc@vger.kernel.org Acked-by: Luis Chamberlain <mcgrof@kernel.org> Link: https://lore.kernel.org/r/20200704034502.17199-6-rdunlap@infradead.org Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-rw-r--r--Documentation/driver-api/firmware/request_firmware.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/driver-api/firmware/request_firmware.rst b/Documentation/driver-api/firmware/request_firmware.rst
index cd076462d235..0d6ea0329995 100644
--- a/Documentation/driver-api/firmware/request_firmware.rst
+++ b/Documentation/driver-api/firmware/request_firmware.rst
@@ -76,5 +76,5 @@ firmware. For example if you used request_firmware() and it returns,
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.