From: Andrew Morton <akpm@linux-foundation.org>
To: Ridong Chen <ridong.chen@linux.dev>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Shakeel Butt <shakeel.butt@linux.dev>,
Chris Li <chrisl@kernel.org>, Kairui Song <kasong@tencent.com>,
Muchun Song <muchun.song@linux.dev>,
Kemeng Shi <shikemeng@huaweicloud.com>,
Nhat Pham <nphamcs@gmail.com>, Baoquan He <baoquan.he@linux.dev>,
Barry Song <baohua@kernel.org>,
Youngjun Park <youngjun.park@lge.com>,
David Hildenbrand <david@kernel.org>,
Qi Zheng <qi.zheng@linux.dev>, Lorenzo Stoakes <ljs@kernel.org>,
Axel Rasmussen <axelrasmussen@google.com>,
Yuanchu Xie <yuanchu@google.com>, Wei Xu <weixugc@google.com>,
Davidlohr Bueso <dave@stgolabs.net>,
cgroups@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Ridong <chenridong@xiaomi.com>
Subject: Re: [PATCH v2 0/2] mm: fix node reclaim swappiness handling
Date: Wed, 22 Jul 2026 18:54:32 -0700 [thread overview]
Message-ID: <20260722185432.12d549d77cbacd8d5e2829f6@linux-foundation.org> (raw)
In-Reply-To: <56fcb7bf-5e0b-46ad-84e5-12b2d00b7a34@linux.dev>
On Thu, 23 Jul 2026 09:13:27 +0800 Ridong Chen <ridong.chen@linux.dev> wrote:
> > include/linux/memcontrol.h | 4 ++--
> > include/linux/swap.h | 19 -------------------
> > mm/memcontrol.c | 4 ++--
> > mm/swap.h | 20 ++++++++++++++++++++
> > mm/vmscan.c | 19 +++++++------------
> > 5 files changed, 31 insertions(+), 35 deletions(-)
> >
>
> Hello all,
>
> Can this series be applied?
>
> Just a reminder in case this gets buried.
Got it, and thanks for the poke.
It seems that kvack.org sent me two of the emails from this 13 email
thread. This is becoming a problem.
next prev parent reply other threads:[~2026-07-23 1:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260716031729.1064007-1-ridong.chen@linux.dev>
[not found] ` <20260716031729.1064007-3-ridong.chen@linux.dev>
[not found] ` <7ddf3eee-5fe2-45f7-8614-c8936a039e04@linux.dev>
[not found] ` <a5eb5433-cf6c-40ee-b14e-128a8bcc85bf@linux.dev>
[not found] ` <94a489d5-8b02-46e6-92d2-ccb85f556769@linux.dev>
2026-07-16 11:17 ` [PATCH v2 2/2] mm: vmscan: fix node reclaim ignoring swappiness parameter Ridong Chen
2026-07-17 2:27 ` Qi Zheng
2026-07-23 1:13 ` [PATCH v2 0/2] mm: fix node reclaim swappiness handling Ridong Chen
2026-07-23 1:54 ` Andrew Morton [this message]
[not found] ` <20260716031729.1064007-2-ridong.chen@linux.dev>
2026-07-23 1:59 ` [PATCH v2 1/2] memcg: move mem_cgroup_swappiness and vm_swappiness to mm/swap.h Johannes Weiner
2026-07-23 2:14 ` 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=20260722185432.12d549d77cbacd8d5e2829f6@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=baohua@kernel.org \
--cc=baoquan.he@linux.dev \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@xiaomi.com \
--cc=chrisl@kernel.org \
--cc=dave@stgolabs.net \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kasong@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=nphamcs@gmail.com \
--cc=qi.zheng@linux.dev \
--cc=ridong.chen@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=shikemeng@huaweicloud.com \
--cc=weixugc@google.com \
--cc=youngjun.park@lge.com \
--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