From: Andrew Morton <akpm@linux-foundation•org>
To: Mark Brown <broonie@kernel•org>
Cc: Mike Rapoport <rppt@kernel•org>,
Ran Xiaokai <ran.xiaokai@zte•com.cn>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: Fixes tags could use some work in the mm-unstable tree
Date: Fri, 13 Mar 2026 09:17:38 -0700 [thread overview]
Message-ID: <20260313091738.354244f6fb500bef3bad1fa1@linux-foundation.org> (raw)
In-Reply-To: <202116fe-2cf1-4399-8324-a028efe27064@sirena.org.uk>
On Fri, 13 Mar 2026 16:08:19 +0000 Mark Brown <broonie@kernel•org> wrote:
> On Fri, Mar 13, 2026 at 09:03:40AM -0700, Andrew Morton wrote:
> > On Fri, 13 Mar 2026 17:32:20 +0200 Mike Rapoport <rppt@kernel•org> wrote:
> > > On Fri, Mar 13, 2026 at 12:11:45PM +0000, Mark Brown wrote:
>
> > > > - No SHA1 recognised
>
> > > Right, sha's in mm-unstable are, well, unstable :(
>
> > > Maybe Andrew's tooling updates those when the patches move to mm-stable...
>
> > I simply remove the hash, but that gets us emails from Mark.
>
> > I actually track the same info in the filename -
> > kho-adopt-radix-tree-for-preserved-memory-tracking-fix.patch fixes
> > kho-adopt-radix-tree-for-preserved-memory-tracking.patch, so I guess
> > it's best for me to just remove the Fixes: line.
>
> I'm guessing that given that it's a fix for a commit in a rebased branch
> it'll get squashed down into the patch it was fixing anyway?
yup, the quilt-level foo-fix.patch gets folded into foo.patch before I
move the patch into non-rebasing git.
prev parent reply other threads:[~2026-03-13 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 12:11 Fixes tags could use some work in the mm-unstable tree Mark Brown
2026-03-13 15:32 ` Mike Rapoport
2026-03-13 16:03 ` Andrew Morton
2026-03-13 16:08 ` Mark Brown
2026-03-13 16:17 ` 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=20260313091738.354244f6fb500bef3bad1fa1@linux-foundation.org \
--to=akpm@linux-foundation$(echo .)org \
--cc=broonie@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=ran.xiaokai@zte$(echo .)com.cn \
--cc=rppt@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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