From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Matthias Brugger <matthias.bgg@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Cc: 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 mediatek tree
Date: Mon, 3 Apr 2023 10:43:37 +0200 [thread overview]
Message-ID: <98a774d3-ade4-72a8-1c6a-3712d596682a@collabora.com> (raw)
In-Reply-To: <20230403175220.5b946b60@canb.auug.org.au>
Il 03/04/23 09:52, Stephen Rothwell ha scritto:
> Hi all,
>
> After merging the mediatek tree, today's linux-next build (arm64
> defconfig) failed like this:
>
> Error: arch/arm64/boot/dts/mediatek/mt6795.dtsi:647.21-22 syntax error
> FATAL ERROR: Unable to parse input tree
>
> Maybe caused by commit
>
> a7c7f1fe2fde ("arm64: dts: mediatek: mt6795: Add MMSYS node for multimedia clocks")
>
> but I don't know how.
>
> I have reverted that commit (and the following 2) for today.
>
Matthias, this issue happens because you didn't apply 07/17 [1] from the
6795/xperia-m5 series...
[1]:
https://lore.kernel.org/all/20230327083647.22017-8-angelogioacchino.delregno@collabora.com/
That contains the mediatek,mt6795-gce.h header that has the definitions used in
a7c7f1fe2fde ("arm64: dts: mediatek: mt6795: Add MMSYS node for multimedia clocks")
....and this is the reason of the syntax error.
Does this commit have to go through devicetree trees?
I'm adding Krzysztof and Rob to the loop for this.
Regards,
Angelo
next prev parent reply other threads:[~2023-04-03 8:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 7:52 linux-next: build failure after merge of the mediatek tree Stephen Rothwell
2023-04-03 8:43 ` AngeloGioacchino Del Regno [this message]
2023-04-03 10:14 ` Krzysztof Kozlowski
2023-04-10 23:24 ` Stephen Rothwell
2023-04-11 16:52 ` Matthias Brugger
-- strict thread matches above, loose matches on Subject: below --
2023-04-03 8:15 Stephen Rothwell
2023-04-03 8:45 ` AngeloGioacchino Del Regno
2023-04-03 9:41 ` AngeloGioacchino Del Regno
2023-04-10 23:25 ` Stephen Rothwell
2023-04-11 16:53 ` Matthias Brugger
2022-08-29 23:42 Stephen Rothwell
2022-08-30 11:10 ` Matthias Brugger
2019-12-15 22:03 Stephen Rothwell
2019-12-16 8:49 ` Matthias Brugger
2019-12-16 9:19 ` Macpaul Lin
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=98a774d3-ade4-72a8-1c6a-3712d596682a@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@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 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).