linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Will Korteland <will@korte.land>
Cc: gregkh@linuxfoundation.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] docs/uio: fix a grammar nitpick
Date: Thu, 18 Oct 2018 12:31:26 -0600	[thread overview]
Message-ID: <20181018123126.3e59c3fd@lwn.net> (raw)
In-Reply-To: <7e426c03c0e342ade7ce86a977ef13b2@korte.land>

On Tue, 16 Oct 2018 08:57:44 +0000 (UTC)
Will Korteland <will@korte.land> wrote:

> This patch fixes a minor, incorrect piece of grammar in the UIO howto.
> 
> Signed-off-by: Will Korteland <will@korte.land>
> Acked-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> The sole change since v1 is that I re-did the patch against
> linux-next-20181016 instead of linux. Sorry for the extra work Greg, and
> thanks Randy for the acked-by.

Unfortunately, this patch is badly white-space mangled.  I tried fixing
it up but eventually had to give up and move on.

Please fix up your email client so that this doesn't happen; see
Documentation/process/email-clients.rst for some helpful suggestions
to that end.  Once you can email the patch to yourself and apply the
result successfully, please resubmit it.

Thanks,

jon
> 
>   Documentation/driver-api/uio-howto.rst | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/driver-api/uio-howto.rst 
> b/Documentation/driver-api/uio-howto.rst
> index fb2eb73be4a3..25f50eace28b 100644
> --- a/Documentation/driver-api/uio-howto.rst
> +++ b/Documentation/driver-api/uio-howto.rst
> @@ -463,8 +463,8 @@ Getting information about your UIO device
> 
>   Information about all UIO devices is available in sysfs. The first 
> thing
>   you should do in your driver is check ``name`` and ``version`` to make
> -sure your talking to the right device and that its kernel driver has 
> the
> -version you expect.
> +sure you're talking to the right device and that its kernel driver has
> +the version you expect.
> 
>   You should also make sure that the memory mapping you need exists and
>   has the size you expect.

  reply	other threads:[~2018-10-18 18:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-16  8:57 [PATCH v2] docs/uio: fix a grammar nitpick Will Korteland
2018-10-18 18:31 ` Jonathan Corbet [this message]
2018-10-19 10:55   ` Will Korteland
2018-10-19 13:18     ` Jonathan Corbet

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=20181018123126.3e59c3fd@lwn.net \
    --to=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=will@korte.land \
    /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).