Drop the doubled word "call".
Signed-off-by: Randy Dunlap <rdun...@infradead.org>
Cc: Jonathan Corbet <cor...@lwn.net>
Cc: linux-...@vger.kernel.org
Cc: Luis Chamberlain <mcg...@kernel.org>
Cc: Greg Kroah-Hartman <gre...@linuxfoundation.org>
---
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.
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-le...@lists.01.org
