From: Zenghui Yu <zenghui.yu@linux.dev>
To: SeongJae Park <sj@kernel.org>
Cc: Zenghui Yu <yuzenghui@huawei.com>,
damon@lists.linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
wangzhigang17@huawei.com, liqiqi23@huawei.com,
stable@vger.kernel.org
Subject: Re: [PATCH v2] samples/damon/mtier: fail early if address range parameters are invalid
Date: Tue, 9 Jun 2026 23:49:07 +0800 [thread overview]
Message-ID: <ed2a595e-bcc4-4af9-99b0-4029f2a13476@linux.dev> (raw)
In-Reply-To: <20260609144918.69429-1-sj@kernel.org>
Hi SeongJae,
On 6/9/26 10:49 PM, SeongJae Park wrote:
>
> I think this deserves Fixes: and Cc: stable, like below.
>
> Fixes: 82a08bde3cf7 ("samples/damon: implement a DAMON module for memory tiering")
> Cc: <stable@vger.kernel.org> # 6.16.x
>
> Other than that, looks good to me.
>
> Reviewed-by: SeongJae Park <sj@kernel.org>
Thanks!
>
> I applied this patch to damon/next [1] tree. We are now quite close to next
> merge window. We (mm community) want to focus on making mm.git more stabilized
> and therefore ready for the next merge window, rather than adding more changes
> that are not really urgent. I understand this series is not really urgent,
> because it is causing only DAMON internal weird behavior and one time warning
> on debug kernels.
Yup!
>
> Hence, Andrew might not add this patch until next -rc1 release. In the case, I
> will request adding this to mm.git after next -rc1 release. So, no action from
> your side is needed for now. Let me know if you think this is really urgent or
> I'm missing something.
I agree with you that this is not urgent and can wait for the next -rc1.
Thanks,
Zenghui
prev parent reply other threads:[~2026-06-09 15:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 6:46 [PATCH v2] samples/damon/mtier: fail early if address range parameters are invalid Zenghui Yu
2026-06-09 14:49 ` SeongJae Park
2026-06-09 15:49 ` Zenghui Yu [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=ed2a595e-bcc4-4af9-99b0-4029f2a13476@linux.dev \
--to=zenghui.yu@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liqiqi23@huawei.com \
--cc=sj@kernel.org \
--cc=stable@vger.kernel.org \
--cc=wangzhigang17@huawei.com \
--cc=yuzenghui@huawei.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