From: Jinjiang Tu <tujinjiang@huawei.com>
To: <akpm@linux-foundation.org>, <david@kernel.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>, <shr@devkernel.io>,
<linux-mm@kvack.org>, <linux-doc@vger.kernel.org>
Cc: <wangkefeng.wang@huawei.com>, <sunnanyong@huawei.com>,
<tujinjiang@huawei.com>
Subject: [PATCH v3 0/2] docs/ksm: fix advisor documentation and comment
Date: Mon, 24 Aug 2026 14:10:08 +0800 [thread overview]
Message-ID: <20260824061010.3343959-1-tujinjiang@huawei.com> (raw)
This series fixes two problems left in the KSM advisor documentation
and code comment:
- Patch 1 fixes two typos in sysfs knob names ("adivsor_max_cpu" and
"adivsor_max_pages_to_scan") in ksm.rst that don't match the actual
knob names.
- Patch 2 fixes the description of advisor_min_pages_to_scan: it is
described as the lower limit of pages_to_scan, but is actually only
used as it's initial value, and the runtime pages_to_scan can drop
below advisor_min_pages_to_scan.
Changes since v2:
* update cover letter
* update commit message for patch2
Changes since v1:
* remove fix tags for both patches
* update commit message and comment for patch2
* collect Acked-by for patch1
Jinjiang Tu (2):
docs: ksm: fix typos in sysfs knob names
mm/ksm: fix advisor_min_pages_to_scan description
Documentation/admin-guide/mm/ksm.rst | 8 ++++----
mm/ksm.c | 2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
--
2.43.0
next reply other threads:[~2026-08-24 6:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 6:10 Jinjiang Tu [this message]
2026-08-24 6:10 ` [PATCH v3 1/2] docs: ksm: fix typos in sysfs knob names Jinjiang Tu
2026-08-24 16:51 ` Randy Dunlap
2026-08-24 6:10 ` [PATCH v3 2/2] mm/ksm: fix advisor_min_pages_to_scan description Jinjiang Tu
2026-08-24 10:10 ` David Hildenbrand (Arm)
2026-08-24 11:03 ` Lorenzo Stoakes (ARM)
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=20260824061010.3343959-1-tujinjiang@huawei.com \
--to=tujinjiang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=chengming.zhou@linux.dev \
--cc=corbet@lwn.net \
--cc=david@kernel.org \
--cc=liam@infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=shr@devkernel.io \
--cc=skhan@linuxfoundation.org \
--cc=sunnanyong@huawei.com \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=wangkefeng.wang@huawei.com \
--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