All of lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 3 Aug 2026 09:54:38 +0200	[thread overview]
Message-ID: <c075be8b-4213-4ba4-8e95-6377986d7c8c@kernel.org> (raw)
In-Reply-To: <fe724e58-f525-4eee-9471-d1765f6bdb0e@huawei.com>

On 8/3/26 09:15, Jinjiang Tu wrote:
> 
> 在 2026/7/31 17:25, David Hildenbrand (Arm) 写道:
>> On 7/31/26 11:22, Jinjiang Tu wrote:
>>> 在 2026/7/31 17:11, David Hildenbrand (Arm) 写道:
>>> 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?
>>
>> :)
> 
> These commits only modify Documentation/ files and contains fix tags.
> 
> 0c13ed77dd2b Docs/admin-guide/mm/damon/lru_sort: warn commit_inputs vs param updates race
> 0beba407d458 Docs/admin-guide/mm/damon/reclaim: warn commit_inputs vs param updates race
> d7f00084f686 Docs/admin-guide/mm/damn/lru_sort: fix intervals autotune parameter name
> 652e1a51465f mm: fix docs for the kernel parameter ``thp_anon=``
> 14e70e4660d6 Docs/admin-guide/mm/damon/usage: fix wrong schemes effective quota update command
> da2a06188888 Docs/admin-guide/mm/damon/usage: fix wrong example of DAMOS filter matching sysfs file
> 1beb8ae302a0 Docs/admin-guide/mm/zswap: remove zsmalloc's lack of writeback warning
> 0ff11f103f5d Docs/admin-guide/mm/damon: rename the title of the document
> 465d0eb0dc31 Docs/admin-guide/mm/damon/usage: fix the example code snip
> 205498012513 Docs/admin-guide/damon/reclaim: remove a paragraph that been obsolete due to online tuning support
> dd21bfa425c0 proc: fix documentation and description of pagemap
> a8db400f997c memory-hotplug.rst: fix wrong /sys/module/memory_hotplug/parameters/ path
> d83fe3c99d27 memory-hotplug.rst: fix two instances of "movablecore" that should be "movable_node"
> 72a3e3e25a51 docs: hugetlbpage.rst: fix some warnings
> 8867f6109b84 docs: fix numaperf.rst and add it to the doc tree
> 
> 
> But there are also commits don't contain fix tags. Such as:
> 
> abdca14655fe Docs/admin-guide/mm/damon: fix 'parametrs' typo
> 78a00cac1e96 docs: fix 're-use' -> 'reuse' in documentation
> eb14b12c8c22 Docs/admin-guide/mm/damon/usage: fix and add missing DAMOS filter sysfs files on files hierarchy
> 472098f23323 docs: mm: fix the incorrect 'FileHugeMapped' field

That is not what I asked. You said "since documentation changes are needed to backport".

Who backports documentation fixes and to which tree?

We usually don't backport anything unless we Cc: stable. And distros don't generally
care that much about documentation backports either.

-- 
Cheers,

David


  reply	other threads:[~2026-08-03  7:54 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)
2026-08-03  7:15         ` Jinjiang Tu
2026-08-03  7:54           ` David Hildenbrand (Arm) [this message]
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=c075be8b-4213-4ba4-8e95-6377986d7c8c@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.