Re: linux-next: build failure after merge of the mm-hotfixes tree

[Mark Brown <broonie@kernel.org>]

[-- Attachment #1: Type: text/plain, Size: 914 bytes --]

On Tue, Apr 21, 2026 at 07:17:01AM -0700, Andrew Morton wrote:
> On Tue, 21 Apr 2026 15:42:29 +0200 "David Hildenbrand (Arm)" <david@kernel.org> wrote:
> > On 4/21/26 15:34, Mark Brown wrote:
> > > On Tue, Apr 21, 2026 at 02:21:48PM +0100, Mark Brown wrote:

> > > And similarly for the mm-nonmm-unstable tree.

> > I think Andrew uses the hotfixes tree as the base for the -unstable
> > trees. So anything that ends up in there gets fast-tracked into -next.
> > Not good :(

> Always been this way.  The expectation is that a hotfix is small,
> time-sensitive and fixes something which is broken in linux-next.  It's
> exceedingly rare for a hotfix to break the build!

> I'll drop this patch.

Thanks.  David, to be clear none of this is much more than a minor
annoyance - I'm just reporting all the trees I'm holding back so there's
a paper trail for anyone who goes looking to figure out why that's been
done.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]