On Fri, Nov 18, 2016 at 1:00 AM, Arnd Bergmann arnd@arndb.de wrote:
On Friday, November 18, 2016 12:31:11 AM CET Olof's autobuilder wrote:
arm64.allmodconfig:/work/build/batch/arch/arm64/boot/dts/qcom/msm8992.dtsi:14:48: fatal error: dt-bindings/clock/qcom,gcc-msm8994.h: No such file or directory /work/build/batch/arch/arm64/boot/dts/qcom/msm8994.dtsi:14:48: fatal error: dt-bindings/clock/qcom,gcc-msm8994.h: No such file or directory /work/build/batch/arch/arm64/boot/dts/qcom/msm8992.dtsi:14:48: fatal error: dt-bindings/clock/qcom,gcc-msm8994.h: No such file or directory /work/build/batch/arch/arm64/boot/dts/qcom/msm8994.dtsi:14:48: fatal error: dt-bindings/clock/qcom,gcc-msm8994.h: No such file or directory
arm64.defconfig:/work/build/batch/arch/arm64/boot/dts/qcom/msm8992.dtsi:14:48: fatal error: dt-bindings/clock/qcom,gcc-msm8994.h: No such file or directory /work/build/batch/arch/arm64/boot/dts/qcom/msm8994.dtsi:14:48: fatal error: dt-bindings/clock/qcom,gcc-msm8994.h: No such file or directory
arm64.nosmp_defconfig:/work/build/batch/arch/arm64/boot/dts/qcom/msm8992.dtsi:14:48: fatal error: dt-bindings/clock/qcom,gcc-msm8994.h: No such file or directory /work/build/batch/arch/arm64/boot/dts/qcom/msm8994.dtsi:14:48: fatal error: dt-bindings/clock/qcom,gcc-msm8994.h: No such file or directory
These must have come in through a missing dependency.
Yeah, Andy pinged me on IRC. I'm increasingly tired of these dependencies that always come up for pretty much any newly introduced SoC.
In this case, the dependency is there to avoid using two numerical constants.
I'm more and more often asking for people to introduce the DTS changes with the constants opencoded, and switch over to the symbolic names after the merge window to avoid this. In this case I'll just merge in the clock branch instead.
-Olof