Re: linux-next: build failure in final build

[Mark Brown]

On Mon, Jan 19, 2026 at 11:37:26PM +0100, Miguel Ojeda wrote:
> On Mon, Jan 19, 2026 at 11:30 PM Mark Brown <broonie@xxxxxxxxxx> 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... :(

Given that all*config (and x86 defconfig) enable CONFIG_WERROR I don't
think this is sustainable, warnings are fatal as far as -next and
general build coverage are concerned.  The tooling can't tell if a build
failure is generated by -Werror or if it's a standard error.

Attachment: signature.asc
Description: PGP signature