From: Andrew Morton <akpm@linux-foundation.org>
To: Sang-Heon Jeon <ekffu200098@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
SeongJae Park <sj@kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the mm-unstable tree
Date: Mon, 18 Aug 2025 18:14:37 -0700 [thread overview]
Message-ID: <20250818181437.318ed154f87f98946203a993@linux-foundation.org> (raw)
In-Reply-To: <CABFDxMHSkmH3LLmZYZN6-Ymj+yRNoaA3=9zg=4P7ZrOxrBs8bg@mail.gmail.com>
On Tue, 19 Aug 2025 09:59:20 +0900 Sang-Heon Jeon <ekffu200098@gmail.com> wrote:
> > has these problem(s):
> >
> > - Target SHA1 does not exist
> >
> > Maybe you meant
> >
> > Fixes: a0b60d083fb6 ("selftests/damon: test no-op commit broke DAMON status")
>
> You're right. I think it might be changed at the point rc1 -> rc2 on
> the mm tree.
> Is there anything I can do? Or maybe Andrew can help?
>
> I didn't mean to bother you guys. Also, original patch is from here [1]
>
> [1] https://lore.kernel.org/all/20250816014033.190451-1-ekffu200098@gmail.com/
I deleted the Fixes: tag. The quilt filename
selftests-damon-test-no-op-commit-broke-damon-status-fix.patch means
"this will be folded into
selftests-damon-test-no-op-commit-broke-damon-status.patch"
next prev parent reply other threads:[~2025-08-19 1:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 21:23 linux-next: Fixes tag needs some work in the mm-unstable tree Stephen Rothwell
2025-08-19 0:59 ` Sang-Heon Jeon
2025-08-19 1:14 ` Andrew Morton [this message]
2025-08-19 1:55 ` Sang-Heon Jeon
2025-08-19 5:39 ` SeongJae Park
2025-08-19 6:33 ` Sang-Heon Jeon
-- strict thread matches above, loose matches on Subject: below --
2025-09-01 22:40 Stephen Rothwell
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=20250818181437.318ed154f87f98946203a993@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ekffu200098@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sj@kernel.org \
/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