From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Jinjiang Tu <tujinjiang@huawei.com>,
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,
shr@devkernel.io, linux-mm@kvack.org, linux-doc@vger.kernel.org
Cc: wangkefeng.wang@huawei.com, sunnanyong@huawei.com
Subject: Re: [PATCH 1/2] docs: ksm: fix typos in sysfs knob names
Date: Fri, 31 Jul 2026 11:25:40 +0200 [thread overview]
Message-ID: <3066dc07-31b5-48ca-b14e-51b284bbb9e1@kernel.org> (raw)
In-Reply-To: <f1f5c486-f14c-44ad-8285-a9df437f7974@huawei.com>
On 7/31/26 11:22, Jinjiang Tu wrote:
>
> 在 2026/7/31 17:11, David Hildenbrand (Arm) 写道:
>> On 7/31/26 10:35, Jinjiang Tu wrote:
>>> The sysfs knob names in mm/ksm.c are "advisor_max_cpu" and
>>> "advisor_max_pages_to_scan", but the ksm.rst documentation spelled
>>> both as "adivsor_*", fix the two typos.
>>>
>>> Fixes: 0710f38ad26a ("mm/ksm: document ksm advisor and its sysfs knobs")
>> I'm not sure on fixes tags for documentation stuff.
>
> git log --grep "Fixes" Documentation/
>
> Many commits in Documentation have fix tag.
> I think both are ok, since documentation changes are needed to backport.
What? When? How? Where?
:)
--
Cheers,
David
next prev parent reply other threads:[~2026-07-31 9:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 8:35 [PATCH 0/2] docs/ksm: fix advisor documentation and comment Jinjiang Tu
2026-07-31 8:35 ` [PATCH 1/2] docs: ksm: fix typos in sysfs knob names Jinjiang Tu
2026-07-31 9:11 ` David Hildenbrand (Arm)
2026-07-31 9:22 ` Jinjiang Tu
2026-07-31 9:25 ` David Hildenbrand (Arm) [this message]
2026-08-03 7:15 ` Jinjiang Tu
2026-08-03 7:54 ` David Hildenbrand (Arm)
2026-08-04 2:15 ` Jinjiang Tu
2026-08-03 7:32 ` Lorenzo Stoakes (ARM)
2026-07-31 8:35 ` [PATCH 2/2] mm/ksm: fix advisor_min_pages_to_scan description Jinjiang Tu
2026-07-31 9:17 ` David Hildenbrand (Arm)
2026-07-31 9:24 ` Jinjiang Tu
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=3066dc07-31b5-48ca-b14e-51b284bbb9e1@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=chengming.zhou@linux.dev \
--cc=corbet@lwn.net \
--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=tujinjiang@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.