docs: fix typo in Documentation/kernel-hacking/locking.rst
PATCH 1/1 docs: fix typo in Documentation/kernel-hacking/locking.rst
Change copy_from_user*( to copy_from_user() .
Signed-off-by Takahiro Itazuri <[email protected]>
--- Documentation/kernel-hacking/locking.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/kernel-hacking/locking.rst +1 -1
@@ -295,7 +295,7 @@ Pete Zaitcev gives the following summary: - If you are in a process context (any syscall) and want to lock other process out, use a mutex. You can take a mutex and sleep - (``copy_from_user*(`` or ``kmalloc(x,GFP_KERNEL)``). + (``copy_from_user()`` or ``kmalloc(x,GFP_KERNEL)``). - Otherwise (== data can be touched in an interrupt), use spin_lock_irqsave() and
Signature · 1 line
2.31.1
Quoted 12 lines · Takahiro Itazuri
Change copy_from_user*( to
copy_from_user().Signed-off-by Takahiro Itazuri <[email protected]>--- Documentation/kernel-hacking/locking.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)Documentation/kernel-hacking/locking.rst +0
-0
Documentation/kernel-hacking/locking.rst Pete Zaitcev gives the following summary: · line 299
Quoted 6 lines
Documentation/kernel-hacking/locking.rst +1
-1@@ -295,7 +295,7 @@ Pete Zaitcev gives the following summary: - If you are in a process context (any syscall) and want to lock other process out, use a mutex. You can take a mutex and sleep - (``copy_from_user*(`` or ``kmalloc(x,GFP_KERNEL)``). + (``copy_from_user()`` or ``kmalloc(x,GFP_KERNEL)``).
Applied, thanks.
jon