Skip to contentSkip to conversation

linux-next: build failure after merge of the fixes tree

DISCUSSION Mark Brown 2 participants 2 messages Oct 2, 2025 Linux-next tree

lore
Share & tools
lore

Mark Brown

author maintainer
#0 lore raw

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")

I have reverted that commit for today and also

639f8e36baf1c ("arm64: dts: exynos: axis: Add initial ARTPEC-8 SoC support")

which depends on it.

#1 lore raw
Quoted 8 lines · Mark Brown

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>

Quoted 7 lines
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

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).