From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
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: Tue, 11 Apr 2023 09:24:12 +1000 [thread overview]
Message-ID: <20230411092412.5a9e20e5@canb.auug.org.au> (raw)
In-Reply-To: <20230403175220.5b946b60@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 580 bytes --]
Hi all,
On Mon, 3 Apr 2023 17:52:20 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> 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.
Ping?
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-04-10 23:31 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
2023-04-03 10:14 ` Krzysztof Kozlowski
2023-04-10 23:24 ` Stephen Rothwell [this message]
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=20230411092412.5a9e20e5@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=angelogioacchino.delregno@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
/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).