From: Mike Rapoport <rppt@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Ran Xiaokai <ran.xiaokai@zte.com.cn>,
Andrew Morton <akpm@linux-foundation.org>,
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 17:32:20 +0200 [thread overview]
Message-ID: <abQuBNBoT_AIfUV7@kernel.org> (raw)
In-Reply-To: <bd8f5814-c5c3-4090-bbc5-9005e2052d9a@sirena.org.uk>
Hi Mark,
On Fri, Mar 13, 2026 at 12:11:45PM +0000, Mark Brown wrote:
> In commit
>
> 5bea10633ca8b ("kho: fix child node parsing for debugfs in/sub_fdts")
>
> Fixes tag
>
> Fixes: "kho: adopt radix tree for preserved memory tracking"
>
> has these problem(s):
>
> - 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...
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2026-03-13 15:32 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 [this message]
2026-03-13 16:03 ` Andrew Morton
2026-03-13 16:08 ` Mark Brown
2026-03-13 16:17 ` Andrew Morton
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=abQuBNBoT_AIfUV7@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ran.xiaokai@zte.com.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.