public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Will Korteland <will@korte.land>
To: corbet@lwn.net, linux-doc@vger.kernel.org
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: [PATCH] docs/uio: fix a grammar nitpick
Date: Mon, 15 Oct 2018 08:10:11 +0000 (UTC)	[thread overview]
Message-ID: <f4edbcfab23ae1a53499dcdc1db32f1b@korte.land> (raw)

This patch fixes a minor, incorrect piece of grammar in the UIO howto.

Signed-off-by: Will Korteland <will@korte.land>
---
This is my first attempt at a kernel patch, so please let me know if
I've done something silly.  I sent a copy of this a few days ago, but
I can't find it on the public archives - apologies if I've now posted
this twice.

  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.
-- 
2.19.1


             reply	other threads:[~2018-10-15  8:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-15  8:10 Will Korteland [this message]
2018-10-15 15:52 ` [PATCH] docs/uio: fix a grammar nitpick Randy Dunlap
     [not found] <3c4f4e78-3557-ce1b-a5f0-cdcefae1fbd3@korte.land>
2018-10-15 18:26 ` Greg KH

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