From: kernel test robot <lkp@intel.com>
To: Hsin-Hsiung Wang <hsin-hsiung.wang@mediatek.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
drinkcat@chromium.org
Cc: kbuild-all@lists.01.org,
Hsin-Hsiung Wang <hsin-hsiung.wang@mediatek.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v3 3/3] arm64: dts: mt8192: add mt6315 regulator nodes
Date: Sun, 27 Dec 2020 16:44:09 +0800 [thread overview]
Message-ID: <202012271647.em0zB2ax-lkp@intel.com> (raw)
In-Reply-To: <1608725624-30594-4-git-send-email-hsin-hsiung.wang@mediatek.com>
[-- Attachment #1: Type: text/plain, Size: 1677 bytes --]
Hi Hsin-Hsiung,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on next-20201223]
[cannot apply to regulator/for-next robh/for-next v5.10 v5.10-rc7 v5.10-rc6 v5.10]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Hsin-Hsiung-Wang/Add-support-for-MT6315-regulator/20201223-201653
base: d7a03a44a5e93f39ece70ec75d25c6088caa0fdb
config: arm64-allyesconfig (attached as .config)
compiler: aarch64-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/5e171b2d898f267bc47e50be27f9e405a2cb173f
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Hsin-Hsiung-Wang/Add-support-for-MT6315-regulator/20201223-201653
git checkout 5e171b2d898f267bc47e50be27f9e405a2cb173f
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> Error: arch/arm64/boot/dts/mediatek/mt8192-evb.dts:27.1-6 Label or path spmi not found
FATAL ERROR: Syntax error parsing input tree
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 76549 bytes --]
prev parent reply other threads:[~2020-12-27 8:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 12:13 [PATCH v3 0/3] Add support for MT6315 regulator Hsin-Hsiung Wang
2020-12-23 12:13 ` [PATCH v3 1/3] dt-bindings: regulator: document binding " Hsin-Hsiung Wang
2020-12-23 17:47 ` Rob Herring
2020-12-31 15:44 ` Rob Herring
2020-12-23 12:13 ` [PATCH v3 2/3] regulator: mt6315: Add support " Hsin-Hsiung Wang
2020-12-24 0:38 ` Nicolas Boichat
2020-12-23 12:13 ` [PATCH v3 3/3] arm64: dts: mt8192: add mt6315 regulator nodes Hsin-Hsiung Wang
2020-12-27 8:44 ` kernel test robot [this message]
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=202012271647.em0zB2ax-lkp@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=drinkcat@chromium.org \
--cc=hsin-hsiung.wang@mediatek.com \
--cc=kbuild-all@lists.01.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).