From: Greg KH <gregkh@linuxfoundation.org>
To: Leno Hou <lenohou@gmail.com>
Cc: stable@vger.kernel.org, Wei Xu <weixugc@google.com>,
Zeng Jingxiang <linuszeng@tencent.com>,
Kairui Song <kasong@tencent.com>, Chris Li <chrisl@kernel.org>,
"T.J. Mercier" <tjmercier@google.com>,
Yu Zhao <yuzhao@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Barry Song <baohua@kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Shakeel Butt <shakeel.butt@linux.dev>,
Axel Rasmussen <axelrasmussen@google.com>,
David Hildenbrand <david@kernel.org>,
"Lorenzo Stoakes (Oracle)" <ljs@kernel.org>,
Michal Hocko <mhocko@kernel.org>,
Qi Zheng <zhengqi.arch@bytedance.com>,
Yuanchu Xie <yuanchu@google.com>
Subject: Re: [PATCH 6.12 0/2] mm: vmscan: fix dirty folios throttling on cgroup v1 for MGLRU
Date: Mon, 26 Oct 2026 19:08:22 +0100 [thread overview]
Message-ID: <2026102643-untried-devotion-b7f7@gregkh> (raw)
In-Reply-To: <CAGQVrL85gG09Uo_+PgGxNOrh+a71eLhsnZn4e93aubpMvXGK5w@mail.gmail.com>
On Mon, Oct 26, 2026 at 11:50:47PM +0800, Leno Hou wrote:
> Sorry, please skip 6.12 branch and just use 6.1 & 6.6 branch
We can't do that, you have to have all patches in all relevant branches
(i.e. you can not just have fixes in older branches, otherwise users
will have regressions when they upgrade.)
thanks,
greg k-h
next prev parent reply other threads:[~2026-10-26 18:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-24 5:35 [PATCH 6.12 0/2] mm: vmscan: fix dirty folios throttling on cgroup v1 for MGLRU Leno Hou via B4 Relay
2026-10-24 5:35 ` [PATCH PATCH 6.12 1/2] mm/vmscan: wake up flushers conditionally to avoid cgroup OOM Leno Hou via B4 Relay
2026-10-24 5:35 ` [PATCH PATCH 6.12 2/2] mm: vmscan: fix dirty folios throttling on cgroup v1 for MGLRU Leno Hou via B4 Relay
2026-10-26 15:50 ` [PATCH 6.12 0/2] " Leno Hou
2026-10-26 18:08 ` Greg KH [this message]
2026-10-27 16:39 ` Leno Hou
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=2026102643-untried-devotion-b7f7@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=chrisl@kernel.org \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kasong@tencent.com \
--cc=lenohou@gmail.com \
--cc=linuszeng@tencent.com \
--cc=ljs@kernel.org \
--cc=mhocko@kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=stable@vger.kernel.org \
--cc=tjmercier@google.com \
--cc=weixugc@google.com \
--cc=yuanchu@google.com \
--cc=yuzhao@google.com \
--cc=zhengqi.arch@bytedance.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