linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: corbet@lwn.net, akpm@linux-foundation.org, bigeasy@linutronix.de,
	ira.weiny@intel.com, rppt@kernel.org,
	Deming Wang <wangdeming@inspur.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Deming Wang <wangdeming@inspur.com>
Subject: Re: [PATCH] mm/highmem: fix spelling mistakeo
Date: Thu, 19 Jan 2023 13:11:19 +0100	[thread overview]
Message-ID: <1841674.tdWV9SEqCh@suse> (raw)
In-Reply-To: <20230118004356.4198-1-wangdeming@inspur.com>

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




      parent reply	other threads:[~2023-01-19 12:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18  0:43 [PATCH] mm/highmem: fix spelling mistakeo Deming Wang
2023-01-18  2:21 ` Bagas Sanjaya
2023-01-18  2:55   ` 答复: " tomorrow Wang (王德明)
2023-01-19  2:11     ` Bagas Sanjaya
2023-01-19 12:11 ` Fabio M. De Francesco [this message]

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=1841674.tdWV9SEqCh@suse \
    --to=fmdefrancesco@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bigeasy@linutronix.de \
    --cc=corbet@lwn.net \
    --cc=ira.weiny@intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rppt@kernel.org \
    --cc=wangdeming@inspur.com \
    /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;
as well as URLs for NNTP newsgroup(s).