linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	trivial@kernel.org
Subject: Re: [PATCH] docs: ioctl: fix typo
Date: Thu, 24 Oct 2019 12:11:52 -0600	[thread overview]
Message-ID: <20191024121152.2004af92@lwn.net> (raw)
In-Reply-To: <20191021014336.14030-1-chris.packham@alliedtelesis.co.nz>

On Mon, 21 Oct 2019 14:43:36 +1300
Chris Packham <chris.packham@alliedtelesis.co.nz> wrote:

> "pointres" should be "pointers".
> 
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> ---
>  Documentation/ioctl/botching-up-ioctls.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/ioctl/botching-up-ioctls.rst b/Documentation/ioctl/botching-up-ioctls.rst
> index ac697fef3545..2d4829b2fb09 100644
> --- a/Documentation/ioctl/botching-up-ioctls.rst
> +++ b/Documentation/ioctl/botching-up-ioctls.rst
> @@ -46,7 +46,7 @@ will need to add a 32-bit compat layer:
>     conversion or worse, fiddle the raw __u64 through your code since that
>     diminishes the checking tools like sparse can provide. The macro
>     u64_to_user_ptr can be used in the kernel to avoid warnings about integers
> -   and pointres of different sizes.
> +   and pointers of different sizes.

Applied, thanks.

jon

      reply	other threads:[~2019-10-24 18:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21  1:43 [PATCH] docs: ioctl: fix typo Chris Packham
2019-10-24 18:11 ` Jonathan Corbet [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191024121152.2004af92@lwn.net \
    --to=corbet@lwn.net \
    --cc=chris.packham@alliedtelesis.co.nz \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trivial@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).