From: Andrew Morton <akpm@linux-foundation.org>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Ruan Shiyang <ruansy.fnst@fujitsu.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org, lkp@intel.com,
ying.huang@linux.alibaba.com, y-goto@fujitsu.com,
mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
rostedt@goodmis.org, mgorman@suse.de, vschneid@redhat.com,
Li Zhijian <lizhijian@fujitsu.com>,
Ben Segall <bsegall@google.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v3] mm: memory-tiering: fix PGPROMOTE_CANDIDATE counting
Date: Mon, 1 Sep 2025 14:00:43 -0700 [thread overview]
Message-ID: <20250901140043.b522b4f16cb4fe52566fe516@linux-foundation.org> (raw)
In-Reply-To: <63a6962f-6ffb-47cd-806d-ec568f0b2df7@suse.cz>
On Mon, 1 Sep 2025 22:34:32 +0200 Vlastimil Babka <vbabka@suse.cz> wrote:
> > Could be either c6833e10008f or c959924b0dc5 afaict. I'll go with
> > c6833e10008f, OK?
>
> LGTM as a helpful pointer, but I don't think Cc: stable is necessary for
> "admin might be confused" kind of thing if that's there since 6.1 and only
> came up now.
OK, thanks.
prev parent reply other threads:[~2025-09-01 21:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 3:51 [PATCH v1] mm: memory-tiering: Fix " Ruan Shiyang
2025-07-30 1:28 ` Huang, Ying
2025-08-29 9:08 ` Vlastimil Babka
2025-08-29 9:18 ` Shiyang Ruan
2025-08-29 9:33 ` Vlastimil Babka
2025-08-30 7:59 ` Vlastimil Babka
2025-09-01 2:05 ` [PATCH v2] mm: memory-tiering: fix " Ruan Shiyang
2025-09-01 8:04 ` Vlastimil Babka
2025-09-01 9:01 ` [PATCH v3] " Ruan Shiyang
2025-09-01 11:09 ` Huang, Ying
2025-09-01 19:59 ` Andrew Morton
2025-09-01 20:34 ` Vlastimil Babka
2025-09-01 21:00 ` Andrew Morton [this message]
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=20250901140043.b522b4f16cb4fe52566fe516@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizhijian@fujitsu.com \
--cc=lkp@intel.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=ruansy.fnst@fujitsu.com \
--cc=stable@vger.kernel.org \
--cc=vbabka@suse.cz \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=y-goto@fujitsu.com \
--cc=ying.huang@linux.alibaba.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