From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Hongfu Li <hongfu.li@linux.dev>,
akpm@linux-foundation.org, xu.xin16@zte.com.cn,
chengming.zhou@linux.dev, ljs@kernel.org, liam@infradead.org,
vbabka@kernel.org, rppt@kernel.org, surenb@google.com,
mhocko@suse.com, corbet@lwn.net, skhan@linuxfoundation.org,
alexs@kernel.org, si.yanteng@linux.dev, dzm91@hust.edu.cn
Cc: linux-mm@kvack.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, Hongfu Li <lihongfu@kylinos.cn>
Subject: Re: [PATCH] ksm: update comments and docs to reference folio->mapping
Date: Wed, 5 Aug 2026 13:05:03 +0200 [thread overview]
Message-ID: <720f8b30-73fb-4983-9bfd-96fc22ebee3b@kernel.org> (raw)
In-Reply-To: <20260805105927.41987-1-hongfu.li@linux.dev>
On 8/5/26 12:59, Hongfu Li wrote:
> From: Hongfu Li <lihongfu@kylinos.cn>
>
> The KSM code already stores and checks the stable node key via
> folio->mapping, but the comment in ksm_get_folio() and the reverse
> mapping documentation in ksm.rst still refer to page->mapping.
>
> This is a pure wording update to match the folio-based implementation.
> No functional change is intended.
>
> Signed-off-by: Hongfu Li <lihongfu@kylinos.cn>
> ---
No idea about the Chinese stuff, but looks correct.
Acked-by: David Hildenbrand (Arm) <david@kernel.org>
--
Cheers,
David
next prev parent reply other threads:[~2026-08-05 11:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 10:59 [PATCH] ksm: update comments and docs to reference folio->mapping Hongfu Li
2026-08-05 11:05 ` David Hildenbrand (Arm) [this message]
2026-08-05 13:00 ` xu.xin16
2026-08-05 13:11 ` Dongliang Mu
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=720f8b30-73fb-4983-9bfd-96fc22ebee3b@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexs@kernel.org \
--cc=chengming.zhou@linux.dev \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=hongfu.li@linux.dev \
--cc=liam@infradead.org \
--cc=lihongfu@kylinos.cn \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=si.yanteng@linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=xu.xin16@zte.com.cn \
/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).