Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Mon, 7 Nov 2022 19:30:48 -0600
From:   Bjorn Andersson <andersson@kernel.org>
To:     Stephen Rothwell <sfr@canb.auug.org.au>
Cc:     Andy Gross <agross@kernel.org>,
        Matti =?utf-8?Q?Lehtim=C3=A4ki?= <matti.lehtimaki@gmail.com>,
        Rayyan Ansari <rayyan@ansari.sh>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the qcom tree
Message-ID: <20221108013048.7uu4gseeysbzpoqt@builder.lan>
References: <20221108090018.44624610@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20221108090018.44624610@canb.auug.org.au>
Precedence: bulk

On Tue, Nov 08, 2022 at 09:00:18AM +1100, 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@fda0c000: Reference to non-existent node or label "mmcc"
> 

Sorry about that, not sure why I didn't catch that before pushing my
branch. I've pulled in the missing patch today.

Thanks,
Bjorn

> Caused by commit
> 
>   4ab2f41b0850 ("ARM: dts: qcom: msm8226: Add CCI bus")
> 
> I have used the qcom tree from next-20221107 for today.
> 
> -- 
> Cheers,
> Stephen Rothwell