From: Ira Weiny <ira.weiny@intel.com>
To: Deming Wang <wangdeming@inspur.com>, <corbet@lwn.net>,
<akpm@linux-foundation.org>, <fmdefrancesco@gmail.com>,
<bigeasy@linutronix.de>, <ira.weiny@intel.com>, <rppt@kernel.org>
Cc: <linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Deming Wang <wangdeming@inspur.com>
Subject: Re: [PATCH] Documentation: mm: use `s/higmem/highmem/` fix typo for highmem
Date: Wed, 18 Jan 2023 09:42:37 -0800 [thread overview]
Message-ID: <63c82f8d56933_985ab294e1@iweiny-mobl.notmuch> (raw)
In-Reply-To: <20230118025403.1531-1-wangdeming@inspur.com>
Deming Wang wrote:
> We should use highmem replace higmem.
>
> Signed-off-by: Deming Wang <wangdeming@inspur.com>
Reviewed-by: Ira Weiny <ira.weiny@intel.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
>
prev parent reply other threads:[~2023-01-18 17:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 2:54 [PATCH] Documentation: mm: use `s/higmem/highmem/` fix typo for highmem Deming Wang
2023-01-18 17:42 ` Ira Weiny [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=63c82f8d56933_985ab294e1@iweiny-mobl.notmuch \
--to=ira.weiny@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=corbet@lwn.net \
--cc=fmdefrancesco@gmail.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