From: kernel test robot <lkp@intel.com>
To: Yash Shah <yash.shah@sifive.com>,
linux-spi@vger.kernel.org, linux-serial@vger.kernel.org,
linux-pwm@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
devicetree@vger.kernel.org, linux-gpio@vger.kernel.org
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
broonie@kernel.org, gregkh@linuxfoundation.org
Subject: Re: [PATCH 4/4] riscv: dts: add initial board data for the SiFive HiFive Unmatched
Date: Thu, 3 Dec 2020 08:43:41 +0800 [thread overview]
Message-ID: <202012030805.Hw1FsK5w-lkp@intel.com> (raw)
In-Reply-To: <1606896236-62780-5-git-send-email-yash.shah@sifive.com>
[-- Attachment #1: Type: text/plain, Size: 2354 bytes --]
Hi Yash,
I love your patch! Yet something to improve:
[auto build test ERROR on robh/for-next]
[also build test ERROR on gpio/for-next wsa/i2c/for-next v5.10-rc6 next-20201201]
[cannot apply to pwm/for-next spi/for-next]
[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/Yash-Shah/arch-riscv-add-board-and-SoC-DT-file-support/20201202-160811
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
config: riscv-randconfig-r016-20201202 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project 2671fccf0381769276ca8246ec0499adcb9b0355)
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
# install riscv cross compiling tool for clang build
# apt-get install binutils-riscv64-linux-gnu
# https://github.com/0day-ci/linux/commit/683dfb5c8d163c4fb3245cad723f8ef4d2305221
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Yash-Shah/arch-riscv-add-board-and-SoC-DT-file-support/20201202-160811
git checkout 683dfb5c8d163c4fb3245cad723f8ef4d2305221
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=riscv
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/riscv/boot/dts/sifive/hifive-unmatched-a00.dts:4:
>> arch/riscv/boot/dts/sifive/fu740-c000.dtsi:6:10: fatal error: 'dt-bindings/clock/sifive-fu740-prci.h' file not found
#include <dt-bindings/clock/sifive-fu740-prci.h>
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
vim +6 arch/riscv/boot/dts/sifive/fu740-c000.dtsi
d3af3c8c2033d2e Yash Shah 2020-12-02 5
d3af3c8c2033d2e Yash Shah 2020-12-02 @6 #include <dt-bindings/clock/sifive-fu740-prci.h>
d3af3c8c2033d2e Yash Shah 2020-12-02 7
---
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: 28663 bytes --]
prev parent reply other threads:[~2020-12-03 0:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 8:03 [PATCH 0/4] arch: riscv: add board and SoC DT file support Yash Shah
2020-12-02 8:03 ` [PATCH 1/4] dt-bindings: riscv: Update DT binding docs to support SiFive FU740 SoC Yash Shah
2020-12-02 13:04 ` Mark Brown
2020-12-02 14:58 ` Andrew Lunn
2020-12-03 6:36 ` Yash Shah
2020-12-02 8:03 ` [PATCH 2/4] riscv: dts: add initial support for the SiFive FU740-C000 SoC Yash Shah
2020-12-02 8:03 ` [PATCH 3/4] dt-bindings: riscv: Update YAML doc to support SiFive HiFive Unmatched board Yash Shah
2020-12-02 8:03 ` [PATCH 4/4] riscv: dts: add initial board data for the SiFive HiFive Unmatched Yash Shah
2020-12-03 0:43 ` 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=202012030805.Hw1FsK5w-lkp@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=yash.shah@sifive.com \
/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).