From: kernel test robot <lkp@intel.com>
To: Luca Weiss <luca.weiss@fairphone.com>
Cc: oe-kbuild-all@lists.linux.dev,
Bjorn Andersson <andersson@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>
Subject: [qcom:arm64-for-6.7 139/142] Error: scripts/dtc/include-prefixes/arm64/qcom/pm7250b.dtsi:44.10-11 syntax error
Date: Thu, 21 Sep 2023 16:10:11 +0800 [thread overview]
Message-ID: <202309211630.0h14xtgj-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux arm64-for-6.7
head: eee9602ad6498eee9ddab1b7eb6aede288f0b934
commit: 8e2d56f64572e0432c355093a7601bde29677490 [139/142] arm64: dts: qcom: pm7250b: make SID configurable
config: arm-defconfig (https://download.01.org/0day-ci/archive/20230921/202309211630.0h14xtgj-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230921/202309211630.0h14xtgj-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/202309211630.0h14xtgj-lkp@intel.com/
All errors (new ones prefixed by >>):
>> Error: scripts/dtc/include-prefixes/arm64/qcom/pm7250b.dtsi:44.10-11 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:[~2023-09-21 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 8:10 kernel test robot [this message]
2023-09-21 8:31 ` [qcom:arm64-for-6.7 139/142] Error: scripts/dtc/include-prefixes/arm64/qcom/pm7250b.dtsi:44.10-11 syntax error Luca Weiss
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=202309211630.0h14xtgj-lkp@intel.com \
--to=lkp@intel.com \
--cc=andersson@kernel.org \
--cc=krzk@kernel.org \
--cc=luca.weiss@fairphone.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.