From: "Matti Lehtimäki" <matti.lehtimaki@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Andy Gross <agross@kernel.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
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
Date: Tue, 8 Nov 2022 00:15:00 +0200 [thread overview]
Message-ID: <fb155814-2e95-3f3b-0826-2c9aed8d0a63@gmail.com> (raw)
In-Reply-To: <20221108090018.44624610@canb.auug.org.au>
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@fda0c000: 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.
>
next prev parent reply other threads:[~2022-11-07 22:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 22:00 linux-next: build failure after merge of the qcom tree Stephen Rothwell
2022-11-07 22:15 ` Matti Lehtimäki [this message]
2022-11-08 1:30 ` Bjorn Andersson
-- strict thread matches above, loose matches on Subject: below --
2023-12-03 23:30 Stephen Rothwell
2023-12-03 23:23 Stephen Rothwell
2023-09-20 22:42 Stephen Rothwell
2023-09-21 6:30 ` Luca Weiss
2021-10-24 23:43 Stephen Rothwell
2021-10-25 2:37 ` Bjorn Andersson
2020-04-15 0:41 Stephen Rothwell
2020-04-15 1:18 ` John Stultz
2020-04-20 23:29 ` Stephen Rothwell
2020-04-21 2:41 ` John Stultz
2020-05-18 5:16 ` Stephen Rothwell
2020-05-18 6:19 ` Bjorn Andersson
2019-04-23 23:25 Stephen Rothwell
2019-04-23 23:50 ` Matthias Kaehlcke
2018-04-25 22:40 Stephen Rothwell
2018-04-26 3:39 ` Evan Green
2018-04-26 4:52 ` Stephen Rothwell
2018-04-26 16:42 ` Evan Green
2018-04-26 21:23 ` Andy Gross
2016-03-31 23:28 Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fb155814-2e95-3f3b-0826-2c9aed8d0a63@gmail.com \
--to=matti.lehtimaki@gmail.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rayyan@ansari.sh \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).