From: kernel test robot <lkp@intel.com>
To: Jens Glathe via B4 Relay
<devnull+jens.glathe.oldschoolsolutions.biz@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Johan Hovold <johan+linaro@kernel.org>,
Aleksandrs Vinarskis <alex.vinarskis@gmail.com>,
Jens Glathe <jens.glathe@oldschoolsolutions.biz>
Subject: Re: [PATCH 4/4] arm64: dts: qcom: x1p42100-lenovo-thinkbook-16: dt definition for Thinkbook 16
Date: Fri, 16 May 2025 21:09:18 +0800 [thread overview]
Message-ID: <202505162035.hYLdjmWr-lkp@intel.com> (raw)
In-Reply-To: <20250515-tb16-dt-v1-4-dc5846a25c48@oldschoolsolutions.biz>
Hi Jens,
kernel test robot noticed the following build errors:
[auto build test ERROR on bdd609656ff5573db9ba1d26496a528bdd297cf2]
url: https://github.com/intel-lab-lkp/linux/commits/Jens-Glathe-via-B4-Relay/dt-bindings-arm-qcom-Add-Lenovo-Thinkbook-16/20250516-044052
base: bdd609656ff5573db9ba1d26496a528bdd297cf2
patch link: https://lore.kernel.org/r/20250515-tb16-dt-v1-4-dc5846a25c48%40oldschoolsolutions.biz
patch subject: [PATCH 4/4] arm64: dts: qcom: x1p42100-lenovo-thinkbook-16: dt definition for Thinkbook 16
config: arm64-randconfig-001-20250516 (https://download.01.org/0day-ci/archive/20250516/202505162035.hYLdjmWr-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 9.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250516/202505162035.hYLdjmWr-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/202505162035.hYLdjmWr-lkp@intel.com/
All errors (new ones prefixed by >>):
>> Error: arch/arm64/boot/dts/qcom/x1p42100-lenovo-thinkbook-16.dts:22.15-30 Label or path pm8010_thermal not found
>> FATAL ERROR: Syntax error parsing input tree
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-05-16 13:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 20:38 [PATCH 0/4] " Jens Glathe via B4 Relay
2025-05-15 20:38 ` [PATCH 1/4] dt-bindings: arm: qcom: Add Lenovo " Jens Glathe via B4 Relay
2025-05-21 9:31 ` Krzysztof Kozlowski
2025-05-21 9:37 ` Jens Glathe
2025-05-15 20:38 ` [PATCH 2/4] firmware: qcom: scm: Allow QSEECOM on " Jens Glathe via B4 Relay
2025-05-15 20:38 ` [PATCH 3/4] arm64: dts: qcom: x1p42100: add Lenovo ThinkBook 16 G7 QOY Jens Glathe via B4 Relay
2025-05-15 20:38 ` [PATCH 4/4] arm64: dts: qcom: x1p42100-lenovo-thinkbook-16: dt definition for Thinkbook 16 Jens Glathe via B4 Relay
2025-05-16 13:09 ` kernel test robot [this message]
2025-05-16 1:43 ` [PATCH 0/4] " Rob Herring (Arm)
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=202505162035.hYLdjmWr-lkp@intel.com \
--to=lkp@intel.com \
--cc=alex.vinarskis@gmail.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=devnull+jens.glathe.oldschoolsolutions.biz@kernel.org \
--cc=jens.glathe@oldschoolsolutions.biz \
--cc=johan+linaro@kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®