[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1841674.tdWV9SEqCh@suse>
Date: Thu, 19 Jan 2023 13:11:19 +0100
From: "Fabio M. De Francesco" <fmdefrancesco@...il.com>
To: corbet@....net, akpm@...ux-foundation.org, bigeasy@...utronix.de,
ira.weiny@...el.com, rppt@...nel.org,
Deming Wang <wangdeming@...pur.com>
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
Deming Wang <wangdeming@...pur.com>
Subject: Re: [PATCH] mm/highmem: fix spelling mistakeo
On mercoledì 18 gennaio 2023 01:43:56 CET Deming Wang wrote:
> Substitute occurrencies of "higmem" with "highmem".
s/occurrencies/occurrences
> 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
> --
> 2.27.0
I think you missed a patch which is already in Andrew's -mm-unstable tree:
[PATCH] mm: Fix two spelling mistakes in highmem.h
https://lore.kernel.org/lkml/20230105121305.30714-1-fmdefrancesco@gmail.com/
Fabio
Powered by blists - more mailing lists