linux-kernel - Re: linux-next: build failure after merge of the fixes 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: <CAGE=qrp_vRvbnVCJ-OQQ3qspEEKqMUoDbGHpimYRBHH0NRig9Q@mail.gmail.com>
Date: Thu, 2 Oct 2025 20:43:28 +0900
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Mark Brown <broonie@...nel.org>
Cc: SeonGu Kang <ksk4725@...sia.com>, Ravi Patel <ravi.patel@...sung.com>, soc@...nel.org, 
	Linus Torvads <torvalds@...ux-foundation.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 fixes tree

On Thu, 2 Oct 2025 at 20:01, Mark Brown <broonie@...nel.org> wrote:
>
> Hi all,
>
> Today's build of Linus' tree (arm64 defconfig) failed like this:
>
> In file included from /tmp/next/build/arch/arm64/boot/dts/exynos/axis/artpec8-grizzly.dts:12:
> /tmp/next/build/arch/arm64/boot/dts/exynos/axis/artpec8.dtsi:12:10: fatal error: dt-bindings/clock/axis,artpec8-clk.h: No such file or directory
>    12 | #include <dt-bindings/clock/axis,artpec8-clk.h>
>       |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> compilation terminated.
> make[5]: *** [/tmp/next/build/scripts/Makefile.dtbs:132: arch/arm64/boot/dts/exynos/axis/artpec8-grizzly.dtb] Error 1
>
> Caused by commit
>
>    b176376991772 ("arm64: dts: axis: Add ARTPEC-8 Grizzly dts support")

 Thanks for the report, I already got message from Linus about it.

This will be "fixed" (not bisectable...)  by clk pull from Stephen.

I'll try to add some more tests for such cases to my CI (because
Samsung won't... ), but it's already a very busy machine. What I
wonder is that this branch was in next for two months and LKP didn't
catch it. Maybe Intel LKP cannot be fully relied on anymore?

It seems it's second missing allmodconfig from LKP this cycle (another
build failure reported by Linus for other pull request).