Linux-Next discussions
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Matthias Brugger <matthias.bgg@gmail.com>,
	AngeloGioacchino Del Regno <angelogioacchino.delregno@kernel.org>,
	Chen-Yu Tsai <wenst@chromium.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the mediatek tree
Date: Wed, 29 Jul 2026 13:30:40 +0100	[thread overview]
Message-ID: <amnycDwBm9e1BLVQ@sirena.org.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 2099 bytes --]

Hi all,

After merging the mediatek tree, today's linux-next build
(arm64 defconfig) failed like this:

Lexical error: /tmp/next/build/arch/arm64/boot/dts/mediatek/mt8173.dtsi:1010.22-33 Unexpected 'CLK_MFG_G3D'
Lexical error: /tmp/next/build/arch/arm64/boot/dts/mediatek/mt8173.dtsi:1011.15-26 Unexpected 'CLK_MFG_MEM'
Lexical error: /tmp/next/build/arch/arm64/boot/dts/mediatek/mt8173.dtsi:1012.15-26 Unexpected 'CLK_MFG_AXI'
FATAL ERROR: Syntax error parsing input tree
make[4]: *** [/tmp/next/build/scripts/Makefile.dtbs:140: arch/arm64/boot/dts/mediatek/mt8173-elm.dtb] Error 1
make[4]: *** Waiting for unfinished jobs....
Lexical error: /tmp/next/build/arch/arm64/boot/dts/mediatek/mt8173.dtsi:1010.22-33 Unexpected 'CLK_MFG_G3D'
Lexical error: /tmp/next/build/arch/arm64/boot/dts/mediatek/mt8173.dtsi:1011.15-26 Unexpected 'CLK_MFG_MEM'
Lexical error: /tmp/next/build/arch/arm64/boot/dts/mediatek/mt8173.dtsi:1012.15-26 Unexpected 'CLK_MFG_AXI'
FATAL ERROR: Syntax error parsing input tree
make[4]: *** [/tmp/next/build/scripts/Makefile.dtbs:140: arch/arm64/boot/dts/mediatek/mt8173-evb.dtb] Error 1
Lexical error: /tmp/next/build/arch/arm64/boot/dts/mediatek/mt8173.dtsi:1010.22-33 Unexpected 'CLK_MFG_G3D'
Lexical error: /tmp/next/build/arch/arm64/boot/dts/mediatek/mt8173.dtsi:1011.15-26 Unexpected 'CLK_MFG_MEM'
Lexical error: /tmp/next/build/arch/arm64/boot/dts/mediatek/mt8173.dtsi:1012.15-26 Unexpected 'CLK_MFG_AXI'
FATAL ERROR: Syntax error parsing input tree
make[4]: *** [/tmp/next/build/scripts/Makefile.dtbs:140: arch/arm64/boot/dts/mediatek/mt8173-elm-hana.dtb] Error 1
Lexical error: /tmp/next/build/arch/arm64/boot/dts/mediatek/mt8173.dtsi:1010.22-33 Unexpected 'CLK_MFG_G3D'
Lexical error: /tmp/next/build/arch/arm64/boot/dts/mediatek/mt8173.dtsi:1011.15-26 Unexpected 'CLK_MFG_MEM'
Lexical error: /tmp/next/build/arch/arm64/boot/dts/mediatek/mt8173.dtsi:1012.15-26 Unexpected 'CLK_MFG_AXI'
FATAL ERROR: Syntax error parsing input tree

Caused by commit

   75bfd9e7cdae0 (arm64: dts: mediatek: mt8173: Add GPU device nodes)

I have used the tree from next-20260728 instead.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2026-07-29 12:30 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-29 12:30 Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-04-15  6:30 linux-next: build failure after merge of the mediatek tree Stephen Rothwell
2025-04-15  7:27 ` AngeloGioacchino Del Regno
2024-06-17 16:44 Mark Brown
2024-06-18  7:49 ` Julien Panis
2024-06-18 10:03   ` AngeloGioacchino Del Regno
2024-06-18 10:20     ` AngeloGioacchino Del Regno
2024-06-18 16:45       ` Julien Panis
2024-06-18 17:42         ` Mark Brown
2024-06-18 18:03         ` Daniel Lezcano
2024-06-19  7:40           ` AngeloGioacchino Del Regno
2024-07-15 17:11             ` Julien Panis
2024-06-18 17:07       ` Kevin Hilman
2024-06-18 11:51     ` Mark Brown
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
2023-04-03  7:52 Stephen Rothwell
2023-04-03  8:43 ` AngeloGioacchino Del Regno
2023-04-03 10:14   ` Krzysztof Kozlowski
2023-04-10 23:24 ` Stephen Rothwell
2023-04-11 16:52   ` 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=amnycDwBm9e1BLVQ@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=angelogioacchino.delregno@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=matthias.bgg@gmail.com \
    --cc=wenst@chromium.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