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] [thread-next>] [day] [month] [year] [list]
Message-ID: <67e5d78c78824176847cc5bb5798e12f@inspur.com>
Date:   Wed, 18 Jan 2023 02:55:11 +0000
From:   tomorrow Wang (王德明) 
        <wangdeming@...pur.com>
To:     "bagasdotme@...il.com" <bagasdotme@...il.com>,
        "corbet@....net" <corbet@....net>,
        "fmdefrancesco@...il.com" <fmdefrancesco@...il.com>,
        "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
        "bigeasy@...utronix.de" <bigeasy@...utronix.de>,
        "ira.weiny@...el.com" <ira.weiny@...el.com>,
        "rppt@...nel.org" <rppt@...nel.org>
CC:     "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: 答复: [PATCH] mm/highmem: fix spelling mistakeo

Hi,

 I find only one typo about higmem. And I have modified the subject.

Thanks

> send: Bagas Sanjaya <bagasdotme@...il.com>
> time: 2023年1月18日 10:21
> to: tomorrow Wang (王德明) <wangdeming@...pur.com>;
> corbet@....net; fmdefrancesco@...il.com; akpm@...ux-foundation.org;
> bigeasy@...utronix.de; ira.weiny@...el.com; rppt@...nel.org
> subject: Re: [PATCH] mm/highmem: fix spelling mistakeo
> 
> On Tue, Jan 17, 2023 at 07:43:56PM -0500, Deming Wang wrote:
> > Substitute occurrencies of "higmem" with "highmem".
> >
> > Signed-off-by: Deming Wang <wangdeming@...pur.com>
> > ---
> >  Documentation/mm/highmem.rst | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/Documentation/mm/highmem.rst
> > b/Documentation/mm/highmem.rst index 59d1078f53df..7da4a0d175f0
> 100644
> > --- a/Documentation/mm/highmem.rst
> > +++ b/Documentation/mm/highmem.rst
> > @@ -83,7 +83,7 @@ list shows them in order of preference of use.
> >    for pages which are known to not come from ZONE_HIGHMEM. However,
> it is
> >    always safe to use kmap_local_page() / kunmap_local().
> >
> > -  While it is significantly faster than kmap(), for the higmem case
> > it
> > +  While it is significantly faster than kmap(), for the highmem case
> > + it
> >    comes with restrictions about the pointers validity. Contrary to kmap()
> >    mappings, the local mappings are only valid in the context of the caller
> >    and cannot be handed to other contexts. This implies that users
> > must
> 
> Are you sure you have seen the other occurences of higmem in the same doc?
> If so, do s/higmem/highmem/g.
> 
> Also, the patch subject prefix should have been Documentation: mm:
> highmem, and also s/mistakeo/mistake/ in the subject.
> 
> Thanks.
> 
> --
> An old man doll... just what I always wanted! - Clara

Download attachment "0001-Documentation-mm-use-s-higmem-highmem-fix-typo-for-h.patch" of type "application/octet-stream" (1178 bytes)

Download attachment "smime.p7s" of type "application/pkcs7-signature" (3780 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ