linux-kernel - Re: linux-next: build failure after merge of the mfd tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <aN1jHx0sgkOFAYM4@finisterre.sirena.org.uk>
Date: Wed, 1 Oct 2025 18:21:35 +0100
From: Mark Brown <broonie@...nel.org>
To: Lee Jones <lee@...nel.org>
Cc: Alexander Stein <alexander.stein@...tq-group.com>,
	Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the mfd tree

On Wed, Oct 01, 2025 at 01:50:28PM +0100, Lee Jones wrote:
> On Wed, 01 Oct 2025, Mark Brown wrote:

> > Your tree gets merged first so we get a build failure when your tree is
> > merged, it would get sorted out eventually when the gpio trees are added
> > but all the intermediate builds are broken.

> Interesting.

> I thought the point of -next was to test everything integrated.

It is, but part of how we do that is we add a tree at a time and see if
they break - there's byproducts of the whole process like pending-fixes
which allows fixes to be tested without all the new work in -next.

> Thanks for the heads-up though.  I'll wait until this has been merged
> before sending out my own PR to Linus.

Note that this has kept everything added after it out of -next.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)