From: kernel test robot <lkp@intel.com>
To: Kathiravan T <kathirav@codeaurora.org>,
agross@kernel.org, bjorn.andersson@linaro.org,
robh+dt@kernel.org, lgirdwood@gmail.com, broonie@kernel.org,
sivaprak@codeaurora.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: kbuild-all@lists.01.org
Subject: Re: [PATCH 3/3] arm64: dts: ipq6018: enable DVFS support
Date: Fri, 31 Jul 2020 05:47:07 +0800 [thread overview]
Message-ID: <202007310503.Oe4Ai6uz%lkp@intel.com> (raw)
In-Reply-To: <1596098964-19878-4-git-send-email-kathirav@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 1630 bytes --]
Hi Kathiravan,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on regulator/for-next]
[cannot apply to robh/for-next v5.8-rc7]
[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/Kathiravan-T/Enable-DVFS-support-for-IPQ6018/20200730-165021
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
config: arm64-defconfig (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
# 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 >>):
In file included from arch/arm64/boot/dts/qcom/ipq6018-cp01-c1.dts:10:
>> arch/arm64/boot/dts/qcom/ipq6018.dtsi:11:10: fatal error: dt-bindings/clock/qcom,apss-ipq.h: No such file or directory
#include <dt-bindings/clock/qcom,apss-ipq.h>
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
vim +11 arch/arm64/boot/dts/qcom/ipq6018.dtsi
> 11 #include <dt-bindings/clock/qcom,apss-ipq.h>
12
---
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: 50230 bytes --]
next prev parent reply other threads:[~2020-07-30 22:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 8:49 [PATCH 0/3] Enable DVFS support for IPQ6018 Kathiravan T
2020-07-30 8:49 ` [PATCH 1/3] dt-bindings: mailbox: add compatible for the IPQ6018 SoC Kathiravan T
2020-07-31 22:28 ` Rob Herring
2020-07-30 8:49 ` [PATCH 2/3] dt-bindings: regulator: add the sub node names for the MP5496 PMIC Kathiravan T
2020-07-30 8:49 ` [PATCH 3/3] arm64: dts: ipq6018: enable DVFS support Kathiravan T
2020-07-30 21:47 ` kernel test robot [this message]
2020-07-30 22:28 ` [PATCH 0/3] Enable DVFS support for IPQ6018 Mark Brown
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=202007310503.Oe4Ai6uz%lkp@intel.com \
--to=lkp@intel.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kathirav@codeaurora.org \
--cc=kbuild-all@lists.01.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sivaprak@codeaurora.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).