All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Chen-Yu Tsai" <wenst@chromium.org>
Cc: oe-kbuild-all@lists.linux.dev,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>
Subject: [mediatek:v7.2-next/dts64 19/19] FATAL ERROR: Syntax error parsing input tree
Date: Thu, 30 Jul 2026 10:23:02 +0800	[thread overview]
Message-ID: <202607301007.06NsJjPi-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/mediatek/linux.git v7.2-next/dts64
head:   75bfd9e7cdae0ae04dbaaf8dfc487adb67b7680e
commit: 75bfd9e7cdae0ae04dbaaf8dfc487adb67b7680e [19/19] arm64: dts: mediatek: mt8173: Add GPU device nodes
config: arm64-randconfig-r111-20260729 (https://download.01.org/0day-ci/archive/20260730/202607301007.06NsJjPi-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 9.5.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260730/202607301007.06NsJjPi-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202607301007.06NsJjPi-lkp@intel.com/

All errors (new ones prefixed by >>):

   Lexical error: arch/arm64/boot/dts/mediatek/mt8173.dtsi:1010.22-33 Unexpected 'CLK_MFG_G3D'
   Lexical error: arch/arm64/boot/dts/mediatek/mt8173.dtsi:1011.15-26 Unexpected 'CLK_MFG_MEM'
   Lexical error: arch/arm64/boot/dts/mediatek/mt8173.dtsi:1012.15-26 Unexpected 'CLK_MFG_AXI'
>> FATAL ERROR: Syntax error parsing input tree

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-07-30  2:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202607301007.06NsJjPi-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --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 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.