From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: FATAL ERROR: Syntax error parsing input tree
Date: Fri, 08 May 2026 07:07:35 +0800 [thread overview]
Message-ID: <202605080736.KVagSyvb-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "bisect to a FBC not belonging to original linux-review patches: branch: linux-review/Michal-Piekos/dt-bindings-timer-allwinner-sun5i-a13-hstimer-add-H616-and-D1/20260507-192013, commit: 11d9dbddad0d7c31df858298cf4715b2a273cd67"
::::::
BCC: lkp@intel.com
CC: llvm@lists.linux.dev
CC: oe-kbuild-all@lists.linux.dev
TO: Michal Piekos <michal.piekos@mmpsystems.pl>
CC: 0day robot <lkp@intel.com>
tree: https://github.com/intel-lab-lkp/linux/commits/Michal-Piekos/dt-bindings-timer-allwinner-sun5i-a13-hstimer-add-H616-and-D1/20260507-192013
head: f7e2fb14161813e667402e7e9f3a3069b84f5664
commit: 11d9dbddad0d7c31df858298cf4715b2a273cd67 arm: dts: allwinner: d1s-t113: add hstimer node
date: 11 hours ago
:::::: branch date: 11 hours ago
:::::: commit date: 11 hours ago
config: riscv-defconfig (https://download.01.org/0day-ci/archive/20260508/202605080736.KVagSyvb-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project 5bac06718f502014fade905512f1d26d578a18f3)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260508/202605080736.KVagSyvb-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/r/202605080736.KVagSyvb-lkp@intel.com/
All errors (new ones prefixed by >>):
Lexical error: arch/riscv/boot/dts/allwinner/sunxi-d1s-t113.dtsi:301.18-25 Unexpected 'GIC_SPI'
Lexical error: arch/riscv/boot/dts/allwinner/sunxi-d1s-t113.dtsi:302.11-18 Unexpected 'GIC_SPI'
>> FATAL ERROR: Syntax error parsing input tree
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-07 23:07 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=202605080736.KVagSyvb-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@lists.linux.dev \
/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.