linux-kernel - Re: linux-next: build failure after merge of the perf 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: <6a8bd632-31ab-4458-8367-bbde59f8f1dd@sirena.org.uk>
Date: Mon, 19 Jan 2026 17:02:38 +0000
From: Mark Brown <broonie@...nel.org>
To: James Clark <james.clark@...aro.org>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@...il.com>,
	Namhyung Kim <namhyung@...nel.org>, Leo Yan <leo.yan@....com>,
	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 perf tree

On Mon, Jan 19, 2026 at 04:55:31PM +0000, James Clark wrote:
> On 19/01/2026 4:43 pm, Mark Brown wrote:

> > No, all the -next builds are done incrementally so the working tree will
> > start with whatever the last commit that got built was.  This would also
> > break bisection cases...

> Oh I see, that's an out of source build path not actually in the repo.

Yeah, all the -next builds are out of tree builds (he says grumpily
looking at the kselftest coverage he just enabled :/) - the source tree
is kept clean.

> That is a problem then, will take a look. I'm not sure why those files are
> even copied out of the tree. It would make sense if they're generated, but
> those ones specifically are not.

> Seems like the build will need to be fixed to either handle deleted files or
> just not copy them in the first place.

Great, thanks.

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