linux-kernel - Re: [PATCH] docs/uio: fix a grammar nitpick

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <ba7b71e7-5652-1209-f169-cacc1067b89a@infradead.org>
Date:   Mon, 15 Oct 2018 08:52:34 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Will Korteland <will@...te.land>, corbet@....net,
        linux-doc@...r.kernel.org
Cc:     gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] docs/uio: fix a grammar nitpick

On 10/15/18 1:10 AM, Will Korteland wrote:
> This patch fixes a minor, incorrect piece of grammar in the UIO howto.
> 
> Signed-off-by: Will Korteland <will@...te.land>

Looks good to me.  Thanks.

Acked-by: Randy Dunlap <rdunlap@...radead.org>


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


-- 
~Randy