[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87k0enwdua.fsf@meer.lwn.net>
Date: Tue, 25 Jan 2022 17:16:45 -0700
From: Jonathan Corbet <corbet@....net>
To: Takahiro Itazuri <itazur@...zon.com>, linux-doc@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, trivial@...nel.org,
Takahiro Itazuri <zulinx86@...il.com>,
Takahiro Itazuri <itazur@...zon.com>
Subject: Re: [PATCH] docs: fix typo in Documentation/kernel-hacking/locking.rst
Takahiro Itazuri <itazur@...zon.com> writes:
> Change copy_from_user*( to copy_from_user() .
>
> Signed-off-by: Takahiro Itazuri <itazur@...zon.com>
> ---
> 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
Powered by blists - more mailing lists