From: kernel test robot <lkp@intel.com>
To: Yixun Lan <dlan@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, 0day robot <lkp@intel.com>
Subject: FATAL ERROR: Syntax error parsing input tree
Date: Thu, 02 Jul 2026 10:53:14 +0200 [thread overview]
Message-ID: <202607021011.Plw2dWcN-lkp@intel.com> (raw)
tree: https://github.com/intel-lab-lkp/linux/commits/Yixun-Lan/scsi-ufs-spacemit-dt-bindings-Add-UFS-controller-for-K3-SoC/20260702-103626
head: 486c1d498ba49051337ead54bb5f3da8982ae5c2
commit: caf19e2a5055c667b4f42a6ca85ffc831390d433 scsi: ufs: spacemit: dt-bindings: Add UFS controller for K3 SoC
date: 6 hours ago
config: openrisc-randconfig-2051-20260702 (https://download.01.org/0day-ci/archive/20260702/202607021011.Plw2dWcN-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 9.5.0
dtschema: 2026.7.dev1+g2203c1720
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260702/202607021011.Plw2dWcN-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/202607021011.Plw2dWcN-lkp@intel.com/
All errors (new ones prefixed by >>):
Lexical error: Documentation/devicetree/bindings/ufs/spacemit,k3-ufshc.example.dts:24.27-46 Unexpected 'CLK_APMU_UFS_REFCLK'
>> FATAL ERROR: Syntax error parsing input tree
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-07-02 8:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 8:53 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-07 23:07 FATAL ERROR: Syntax error parsing input tree kernel test robot
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=202607021011.Plw2dWcN-lkp@intel.com \
--to=lkp@intel.com \
--cc=dlan@kernel.org \
--cc=oe-kbuild-all@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.