From: kernel test robot <lkp@intel.com>
To: Alice Guo <alice.guo@nxp.com>
Cc: oe-kbuild-all@lists.linux.dev, 0day robot <lkp@intel.com>
Subject: FATAL ERROR: Unable to parse input tree
Date: Wed, 20 May 2026 19:16:02 +0200 [thread overview]
Message-ID: <202605201924.kW49enlc-lkp@intel.com> (raw)
tree: https://github.com/intel-lab-lkp/linux/commits/alice-guo-oss-nxp-com/arm64-dts-freescale-add-bootph-all-to-ULP-watchdog-nodes-for-i-MX-platforms/20260519-191349
head: 6e7cb66ece024d1282d112c147cc5e6137c45b34
commit: 6e7cb66ece024d1282d112c147cc5e6137c45b34 arm64: dts: freescale: add ULP watchdog nodes for i.MX platforms
date: 30 hours ago
config: arm-randconfig-2055-20260519 (https://download.01.org/0day-ci/archive/20260520/202605201924.kW49enlc-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project f43d6834093b19baf79beda8c0337ab020ac5f17)
dtschema: 2026.5.dev9+gdf9ad30c5
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260520/202605201924.kW49enlc-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/202605201924.kW49enlc-lkp@intel.com/
All errors (new ones prefixed by >>):
Error: arch/arm/boot/dts/nxp/imx/imx7ulp.dtsi:337.14-15 syntax error
>> FATAL ERROR: Unable to parse input tree
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-05-20 17:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 17:16 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-14 4:30 FATAL ERROR: Unable to parse input tree kernel test robot
2022-01-14 4:30 ` kernel test robot
2014-06-03 12:53 Pacman du34
[not found] ` <CAPH+8+gzCmV=tZOhq3DhYfWo6Pngcj+9XW3gNgCTV+qq5HnJ_Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-03 13:02 ` Mark Rutland
2014-06-03 13:25 ` Pacman du34
[not found] ` <CAPH+8+iDZ3+bx5zU6aoGDH_tiKCPAf07QGymSRp0oB1W+_1=1Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-03 13:35 ` Mark Rutland
2014-06-03 14:35 ` Pacman du34
[not found] ` <CAPH+8+giheV1kcuOAHvUWuDGRL4e2wRO95KJRxA9-o=TRVZ5FQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-03 14:51 ` Mark Rutland
2014-06-03 15:04 ` Pacman du34
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=202605201924.kW49enlc-lkp@intel.com \
--to=lkp@intel.com \
--cc=alice.guo@nxp.com \
--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.