Thread (4 messages) flat view 4 messages, 2 authors, 2021-10-25
STALE1782d LANDED

Landed in mainline as 33ef298651e9 on 2021-10-25.

[PATCH 2/2] Docs: usb: remove :c:func: for usb_register and usb_deregister

From: Philipp Hortmann <hidden>
Date: 2021-10-25 05:10:01
Also in: linux-usb, lkml
Subsystem: documentation, the rest · Maintainers: Jonathan Corbet, Linus Torvalds

remove :c:func: for usb_register and usb_deregister

Signed-off-by: Philipp Hortmann <redacted>
---
 Documentation/driver-api/usb/writing_usb_driver.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/driver-api/usb/writing_usb_driver.rst b/Documentation/driver-api/usb/writing_usb_driver.rst
index a511c6fecf96..e09dac9e2cb6 100644
--- a/Documentation/driver-api/usb/writing_usb_driver.rst
+++ b/Documentation/driver-api/usb/writing_usb_driver.rst
@@ -84,7 +84,7 @@ this user-space interaction. The skeleton driver needs this kind of
 interface, so it provides a minor starting number and a pointer to its
 :c:type:`file_operations` functions.
 
-The USB driver is then registered with a call to :c:func:`usb_register`,
+The USB driver is then registered with a call to usb_register(),
 usually in the driver's init function, as shown here::
 
     static int __init usb_skel_init(void)
@@ -105,7 +105,7 @@ usually in the driver's init function, as shown here::
 
 
 When the driver is unloaded from the system, it needs to deregister
-itself with the USB subsystem. This is done with the :c:func:`usb_deregister`
+itself with the USB subsystem. This is done with usb_deregister()
 function::
 
     static void __exit usb_skel_exit(void)
-- 
2.25.1
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help