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(-)
diff --git a/Documentation/kernel-hacking/locking.rst b/Documentation/kernel-hacking/locking.rst
index e6cd40663ea5..4cbd50edf277 100644
--- a/Documentation/kernel-hacking/locking.rst
+++ b/Documentation/kernel-hacking/locking.rst
@@ -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
--
2.31.1
Takahiro Itazuri <[email protected]> writes:
> 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(-)
>
> diff --git a/Documentation/kernel-hacking/locking.rst b/Documentation/kernel-hacking/locking.rst
> index e6cd40663ea5..4cbd50edf277 100644
> --- a/Documentation/kernel-hacking/locking.rst
> +++ b/Documentation/kernel-hacking/locking.rst
> @@ -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