From: Andre Przywara <andre.przywara@arm.com>
To: "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail.com>
Cc: Jernej Skrabec <jernej.skrabec@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: mainline build failure due to e1d7dc52c3e6 ("ARM: dts: suniv: f1c100s: add CIR DT node")
Date: Tue, 13 Dec 2022 17:10:02 +0000 [thread overview]
Message-ID: <20221213171002.23c8c712@donnerap.cambridge.arm.com> (raw)
In-Reply-To: <Y5hZcmnZHsgpv3Pu@debian>
On Tue, 13 Dec 2022 10:52:34 +0000
"Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail.com> wrote:
Hi Sudip,
thanks for the heads up.
> The latest mainline kernel branch fails to build arm allmodconfig and
> multi_v5_defconfig with the error:
>
> Error: arch/arm/boot/dts/suniv-f1c100s.dtsi:250.30-31 syntax error
> FATAL ERROR: Unable to parse input tree
This is because the clock patch hasn't reached Linus' tree yet, as it's
coming from a different branch:
https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git/log/?h=sunxi/clk-for-6.2
In the original series I had it in the right order, but I guess the single
line to add the "CLK_IR" symbol should have been in a separate patch and
gone along with the DT patches.
Anyway it should magically solve itself in the next hours/days, I guess.
Cheers,
Andre
> git bisect pointed to e1d7dc52c3e6 ("ARM: dts: suniv: f1c100s: add CIR DT node")
>
> I will be happy to test any patch or provide any extra log if needed.
>
>
next prev parent reply other threads:[~2022-12-13 17:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 10:52 mainline build failure due to e1d7dc52c3e6 ("ARM: dts: suniv: f1c100s: add CIR DT node") Sudip Mukherjee (Codethink)
2022-12-13 17:10 ` Andre Przywara [this message]
2022-12-13 18:27 ` Krzysztof Kozlowski
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=20221213171002.23c8c712@donnerap.cambridge.arm.com \
--to=andre.przywara@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.org \
/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).