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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20251001125028.GS8757@google.com>
Date: Wed, 1 Oct 2025 13:50:28 +0100
From: Lee Jones <lee@...nel.org>
To: Mark Brown <broonie@...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, 01 Oct 2025, Mark Brown wrote:

> On Wed, Oct 01, 2025 at 10:51:08AM +0100, Lee Jones wrote:
> > On Wed, 17 Sep 2025, Mark Brown wrote:
> 
> > > After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
> > > failed like this:
> 
> > > Caused by commit
> 
> > >    df6a44003953f ("mfd: stmpe: Allow building as module")
> 
> > > which needs commit
> 
> > >    03db20aaa3ba3 ("gpio: stmpe: Allow to compile as a module")
> 
> > > from the gpio tree.  I have used the version from yesterday instead.
> 
> > Isn't the later already in -next?
> 
> 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.

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

-- 
Lee Jones [李琼斯]