[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <63c82f8d56933_985ab294e1@iweiny-mobl.notmuch>
Date: Wed, 18 Jan 2023 09:42:37 -0800
From: Ira Weiny <ira.weiny@...el.com>
To: Deming Wang <wangdeming@...pur.com>, <corbet@....net>,
<akpm@...ux-foundation.org>, <fmdefrancesco@...il.com>,
<bigeasy@...utronix.de>, <ira.weiny@...el.com>, <rppt@...nel.org>
CC: <linux-doc@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
Deming Wang <wangdeming@...pur.com>
Subject: Re: [PATCH] Documentation: mm: use `s/higmem/highmem/` fix typo for
highmem
Deming Wang wrote:
> We should use highmem replace higmem.
>
> Signed-off-by: Deming Wang <wangdeming@...pur.com>
Reviewed-by: Ira Weiny <ira.weiny@...el.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
> --
> 2.27.0
>
Powered by blists - more mailing lists