From: Ridong Chen <ridong.chen@linux.dev>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Shakeel Butt <shakeel.butt@linux.dev>,
Muchun Song <muchun.song@linux.dev>, Chris Li <chrisl@kernel.org>,
Kairui Song <kasong@tencent.com>,
David Hildenbrand <david@kernel.org>,
Barry Song <baohua@kernel.org>, Yuanchu Xie <yuanchu@google.com>,
linux-mm@kvack.org, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org, Ridong Chen <chenridong@xiaomi.com>
Subject: Re: [PATCH 2/2] mm: vmscan: fix node reclaim ignoring swappiness parameter
Date: Tue, 14 Jul 2026 15:58:04 +0800 [thread overview]
Message-ID: <0f52a483-27d1-480a-bb0c-99c108e676b5@linux.dev> (raw)
In-Reply-To: <20260713112803.GF276793@cmpxchg.org>
Hi Johannes,
> Probably warrants a stable CC for 6.16 as well since this is pretty
> user-visible breakage.
Thanks for the stable tag suggestion.
I checked the commit baseline:
git name-rev b980077899ea
b980077899ea tags/v6.17-rc1
So this should be tagged for 6.17+ rather than 6.16. I'll add:
Cc: stable@vger.kernel.org # 6.17+
--
Best regards
Ridong
next prev parent reply other threads:[~2026-07-14 7:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-11 9:11 [PATCH 0/2] mm: fix node reclaim swappiness handling Ridong Chen
2026-07-11 9:11 ` [PATCH 1/2] memcg: move mem_cgroup_swappiness to memcontrol.h Ridong Chen
2026-07-13 15:08 ` Barry Song
2026-07-14 1:19 ` Ridong Chen
2026-07-14 1:43 ` Barry Song
2026-07-14 1:48 ` Barry Song
2026-07-14 7:42 ` Ridong Chen
2026-07-14 10:21 ` Barry Song
2026-07-14 11:31 ` Ridong Chen
2026-07-14 13:46 ` Barry Song
2026-07-11 9:11 ` [PATCH 2/2] mm: vmscan: fix node reclaim ignoring swappiness parameter Ridong Chen
2026-07-13 11:28 ` Johannes Weiner
2026-07-14 7:58 ` Ridong Chen [this message]
[not found] ` <CAGsJ_4xGKM3HxXw-mrtyr5HmwZL3L1QVZ27utCyozqSJr1F0gQ@mail.gmail.com>
2026-07-14 1:10 ` Ridong Chen
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=0f52a483-27d1-480a-bb0c-99c108e676b5@linux.dev \
--to=ridong.chen@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@xiaomi.com \
--cc=chrisl@kernel.org \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kasong@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=yuanchu@google.com \
/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