From: "Luca Weiss" <luca.weiss@fairphone.com>
To: "Stephen Rothwell" <sfr@canb.auug.org.au>,
"Andy Gross" <agross@kernel.org>
Cc: "Bjorn Andersson" <andersson@kernel.org>,
"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: Thu, 21 Sep 2023 08:30:08 +0200 [thread overview]
Message-ID: <CVODTTU89L11.Y3SSDO2Y9A35@otso> (raw)
In-Reply-To: <20230921084252.3c5ab501@canb.auug.org.au>
On Thu Sep 21, 2023 at 12:42 AM CEST, Stephen Rothwell wrote:
> Hi all,
>
> After merging the qcom tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> Error: scripts/dtc/include-prefixes/arm64/qcom/pm7250b.dtsi:44.10-11 syntax error
> FATAL ERROR: Unable to parse input tree
>
> Caused (exposed) by commit
>
> eee9602ad649 ("arm64: dts: qcom: qcm6490: Add device-tree for Fairphone 5")
Hi, this should be caused by
"arm64: dts: qcom: pm7250b: make SID configurable"
It seems I've missed updating one arm32 dts file, I'll send a patch for
this shortly.
Sorry about that.
diff --git a/arch/arm/boot/dts/qcom/qcom-sdx65-mtp.dts b/arch/arm/boot/dts/qcom/qcom-sdx65-mtp.dts
index fcf1c51c5e7a..9649c859a2c3 100644
--- a/arch/arm/boot/dts/qcom/qcom-sdx65-mtp.dts
+++ b/arch/arm/boot/dts/qcom/qcom-sdx65-mtp.dts
@@ -4,6 +4,10 @@
*/
/dts-v1/;
+/* PM7250B is configured to use SID2/3 */
+#define PM7250B_SID 2
+#define PM7250B_SID1 3
+
#include "qcom-sdx65.dtsi"
#include <dt-bindings/regulator/qcom,rpmh-regulator.h>
#include <arm64/qcom/pmk8350.dtsi>
>
> I have used the qcom tree from next-20230920 for today.
next prev parent reply other threads:[~2023-09-21 20:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 22:42 linux-next: build failure after merge of the qcom tree Stephen Rothwell
2023-09-21 6:30 ` Luca Weiss [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-17 13:31 Mark Brown
2026-07-17 14:03 ` Konrad Dybcio
2026-07-09 14:21 Mark Brown
2024-08-01 23:48 Stephen Rothwell
2024-08-05 6:39 ` Satya Priya Kakitapalli (Temp)
2024-06-25 11:36 Mark Brown
2024-07-01 1:22 ` Stephen Rothwell
2023-12-03 23:30 Stephen Rothwell
2023-12-03 23:30 ` Stephen Rothwell
2023-12-03 23:23 Stephen Rothwell
2022-11-07 22:00 Stephen Rothwell
2022-11-07 22:15 ` Matti Lehtimäki
2022-11-08 1:30 ` Bjorn Andersson
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=CVODTTU89L11.Y3SSDO2Y9A35@otso \
--to=luca.weiss@fairphone.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.