From: SJ Park <sj@kernel.org>
To: SJ Park <sj@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, patches@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
Brendan Higgins <brendan.higgins@linux.dev>,
David Gow <davidgow@davidgow.net>,
Usama Arif <usamaarif642@gmail.com>,
Sasha Levin <sashal@kernel.org>,
damon@lists.linux.dev
Subject: Re: [PATCH 7.3 0655/1257] mm/damon/core-kunit: test invalid damos filter commits
Date: Sat, 7 Nov 2026 10:36:49 -0800 [thread overview]
Message-ID: <20261107183650.177635-1-sj@kernel.org> (raw)
In-Reply-To: <20261107183202.177477-1-sj@kernel.org>
On Sat, 07 Nov 2026 10:32:10 -0800 SJ Park <sj@kernel.org> wrote:
> Hi Greg,
>
> On Sat, 7 Nov 2026 08:49:11 -0500 Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
>
> > 7.3-stable review patch. If anyone has any objections, please let me know.
>
> TL;DR: Please drop this. It has wrong Cc: stable@ tag.
>
> >
> > ------------------
> >
> > From: SJ Park <sj@kernel.org>
> >
> > [ Upstream commit 409d2ab6d98209c30d45123920721710475a30b4 ]
> >
> > Add test cases for testing the validation of damos filter arguments in
> > commit time.
>
> This patch is for testing commit 1bfb9384ae0e ("mm/damon/core: disallow max <
> min damos filter range arguments commit"), which does not exist in 7.3.y.
> Hence this patch is making DAMON kunit fails.
>
> >
> > Link: https://lore.kernel.org/20260914142327.92510-9-sj@kernel.org
> > Signed-off-by: SJ Park <sj@kernel.org>
> > Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> > Cc: Brendan Higgins <brendan.higgins@linux.dev>
> > Cc: David Gow <davidgow@davidgow.net>
> > Cc: Usama Arif <usamaarif642@gmail.com>
> > Cc: <stable@vger.kernel.org>
>
> I didn't intend this to be applied to stable@. My original patch [1] hence
> doesn't have Cc: stable@. But I show Cc: stable@ tag in the upstream commit.
> Seems Andrew added Cc: stable@ while applying it to mm.git and I missed it.
> Sorry for not catching this early.
>
> So, this patch is not really meant to be picked into stable@, and only causing
> the kunit failure. Could you please drop this?
FWIW, the patch was posted as a part of a series that have a few Cc: stable@
patches. I did so because Cc: stable@ patches are only for minor bug fixes
that does not require the fast path of hotfixes. Apparently it only confused
Andrew or his script. Sorry about that. I will not mix Cc: stable@ patches
with non-Cc: stable@ patches from the next time.
>
> [1] https://lore.kernel.org/20260914142327.92510-9-sj@kernel.org
>
>
> Thanks,
> SJ
>
> [...]
>
Thanks,
SJ
parent reply other threads:[~2026-11-07 18:37 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20261107183202.177477-1-sj@kernel.org>]
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=20261107183650.177635-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=brendan.higgins@linux.dev \
--cc=damon@lists.linux.dev \
--cc=davidgow@davidgow.net \
--cc=gregkh@linuxfoundation.org \
--cc=patches@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=usamaarif642@gmail.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