linux-kernel - Re: linux-next: build failure after merge of the qcom 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: <20221108013048.7uu4gseeysbzpoqt@builder.lan>
Date:   Mon, 7 Nov 2022 19:30:48 -0600
From:   Bjorn Andersson <andersson@...nel.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Andy Gross <agross@...nel.org>,
        Matti Lehtimäki <matti.lehtimaki@...il.com>,
        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

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@...0c000: 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