linux-kernel - Re: linux-next: build failure after merge of the tip 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: <20251112104814.GB3245006@noisy.programming.kicks-ass.net>
Date: Wed, 12 Nov 2025 11:48:14 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...nel.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	Dapeng Mi <dapeng1.mi@...ux.intel.com>,
	Kan Liang <kan.liang@...ux.intel.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 tip tree

On Wed, Nov 12, 2025 at 09:45:15PM +1100, Stephen Rothwell wrote:
> Hi Peter,
> 
> On Wed, 12 Nov 2025 10:39:28 +0100 Peter Zijlstra <peterz@...radead.org> wrote:
> > 
> > It appears you're way faster than the build robots :/
> 
> I was hoping people would put their code through the robots (or some
> local unit testing) before publishing it in their linux-next included
> branches ... ;-)

I do, but sometimes they just take forever :/ And clearly I don't do
i386 builds myself.