[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fb155814-2e95-3f3b-0826-2c9aed8d0a63@gmail.com>
Date: Tue, 8 Nov 2022 00:15:00 +0200
From: Matti Lehtimäki <matti.lehtimaki@...il.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
Andy Gross <agross@...nel.org>
Cc: Bjorn Andersson <andersson@...nel.org>,
Rayyan Ansari <rayyan@...ari.sh>,
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 qcom tree
Hi,
This happened because one of the dts patches in the patch series which
contained "ARM: dts: qcom: msm8226: Add CCI bus" was not applied when
the other two dts patches were applied qcom tree. The patch number 1
"ARM: dts: qcom: msm8226: Add MMCC node" in that patch series
(https://lore.kernel.org/linux-arm-msm/20221002122859.75525-1-matti.lehtimaki@gmail.com/T/#m920039b455ad024249d000332d1f07f9e4c19008)
is required for that "ARM: dts: qcom: msm8226: Add CCI bus".
--
Matti Lehtimäki
On 8.11.2022 0.00, Stephen Rothwell wrote:
> Hi all,
>
> After merging the qcom tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> arch/arm/boot/dts/qcom-msm8226.dtsi:302.21-327.5: ERROR (phandle_references): /soc/cci@...0c000: Reference to non-existent node or label "mmcc"
>
> Caused by commit
>
> 4ab2f41b0850 ("ARM: dts: qcom: msm8226: Add CCI bus")
>
> I have used the qcom tree from next-20221107 for today.
>
Powered by blists - more mailing lists