linux-kernel - Re: linux-next: build failure in final build

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: <CANiq72=xTpfYAdY3oHRG8c8akOwKGHo=kHXk4L71m0TxAXv4Aw@mail.gmail.com>
Date: Mon, 19 Jan 2026 23:37:26 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Mark Brown <broonie@...nel.org>
Cc: Alice Ryhl <aliceryhl@...gle.com>, Daniel Almeida <daniel.almeida@...labora.com>, 
	Deborah Brouwer <deborah.brouwer@...labora.com>, Danilo Krummrich <dakr@...nel.org>, 
	Miguel Ojeda <ojeda@...nel.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 in final build

On Mon, Jan 19, 2026 at 11:30 PM Mark Brown <broonie@...nel.org> wrote:
>
> at which point I gave up and marked the driver as BROKEN for today, I
> might take another look tomorrow.

If they are "just" warnings like the latter ones (i.e. CONFIG_WERROR
is enabled), then I guess one option is to leave them there for a
cycle or two, but I don't know that can be easily tracked to avoid
trees accumulating them... :(

> I note that the dependency that the rust DRM drivers have on DRM=y means
> that they evade allmodconfig build coverage which is not playing well
> here.  I will move the drm-rust and drm-nova trees to be the last trees
> merged to mitigate this issue, their fixes trees will still be affected.

Yeah, sorry about that -- it is a requirement at the moment, but it
will be lifted with build system changes soon.

Cheers,
Miguel