linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ira Weiny <ira.weiny@intel.com>
To: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Alexander Potapenko <glider@google.com>,
	"Bagas Sanjaya" <bagasdotme@gmail.com>,
	Andrey Konovalov <andreyknvl@gmail.com>,
	Tony Luck <tony.luck@intel.com>, <linux-kernel@vger.kernel.org>,
	"Matthew Wilcox (Oracle)" <willy@infradead.org>,
	<linux-mm@kvack.org>
Subject: Re: [PATCH v2] mm: Remove an ambiguous sentence from kmap_local_folio() kdocs
Date: Thu, 5 Jan 2023 08:58:59 -0800	[thread overview]
Message-ID: <Y7cB069naGgBCTIA@iweiny-desk3> (raw)
In-Reply-To: <20230105120424.30055-1-fmdefrancesco@gmail.com>

On Thu, Jan 05, 2023 at 01:04:24PM +0100, Fabio M. De Francesco wrote:
> In the kdocs of kmap_local_folio() there is a an ambiguous sentence
> which suggests to use this API "only when really necessary".
> 
> On the contrary, since kmap() and kmap_atomic() are deprecated, both
> kmap_local_folio(), as well as kmap_local_page(), must be preferred
> to the previous ones.
> 
> Therefore, remove the above-mentioned sentence exactly how it has
> previously been done for the kmap_local_page() kdocs in
> commit 72f1c55adf70 ("highmem: delete a sentence from kmap_local_page() kdocs").
> 
> Cc: Ira Weiny <ira.weiny@intel.com>

Reviewed-by: Ira Weiny <ira.weiny@intel.com>

> Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
> Signed-off-by: Fabio M. De Francesco <fmdefrancesco@gmail.com>
> ---
>  include/linux/highmem.h | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/include/linux/highmem.h b/include/linux/highmem.h
> index 44242268f53b..7b0085a61e67 100644
> --- a/include/linux/highmem.h
> +++ b/include/linux/highmem.h
> @@ -120,8 +120,7 @@ static inline void *kmap_local_page(struct page *page);
>   * temporarily mapped.
>   *
>   * While it is significantly faster than kmap() for the higmem case it
> - * comes with restrictions about the pointer validity. Only use when really
> - * necessary.
> + * comes with restrictions about the pointer validity.
>   *
>   * On HIGHMEM enabled systems mapping a highmem page has the side effect of
>   * disabling migration in order to keep the virtual address stable across
> -- 
> 2.39.0
> 


      reply	other threads:[~2023-01-05 16:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05 12:04 [PATCH v2] mm: Remove an ambiguous sentence from kmap_local_folio() kdocs Fabio M. De Francesco
2023-01-05 16:58 ` 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=Y7cB069naGgBCTIA@iweiny-desk3 \
    --to=ira.weiny@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=andreyknvl@gmail.com \
    --cc=bagasdotme@gmail.com \
    --cc=bigeasy@linutronix.de \
    --cc=fmdefrancesco@gmail.com \
    --cc=glider@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=tony.luck@intel.com \
    --cc=willy@infradead.org \
    /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).