From: kbuild test robot <lkp@intel.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: kbuild-all@lists.01.org, linux-amlogic@lists.infradead.org,
khilman@baylibre.com, jbrunet@baylibre.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Subject: Re: [PATCH 2/3] ARM: dts: meson8: add the DDR clock controller
Date: Mon, 9 Dec 2019 11:20:13 +0800 [thread overview]
Message-ID: <201912091038.s62HNGKV%lkp@intel.com> (raw)
In-Reply-To: <20191208180525.1076152-3-martin.blumenstingl@googlemail.com>
[-- Attachment #1: Type: text/plain, Size: 1913 bytes --]
Hi Martin,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on robh/for-next]
[also build test ERROR on v5.5-rc1 next-20191208]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Martin-Blumenstingl/ARM-dts-meson-clock-updates/20191209-020750
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
config: arm-allmodconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (GCC) 7.5.0
reproduce:
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
GCC_VERSION=7.5.0 make.cross ARCH=arm
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from arch/arm/boot/dts/meson8-minix-neo-x8.dts:8:
>> arch/arm/boot/dts/meson8.dtsi:6:10: fatal error: dt-bindings/clock/meson8-ddr-clkc.h: No such file or directory
6 | #include <dt-bindings/clock/meson8-ddr-clkc.h>
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
vim +6 arch/arm/boot/dts/meson8.dtsi
> 6 #include <dt-bindings/clock/meson8-ddr-clkc.h>
7 #include <dt-bindings/clock/meson8b-clkc.h>
8 #include <dt-bindings/gpio/meson8-gpio.h>
9 #include <dt-bindings/reset/amlogic,meson8b-clkc-reset.h>
10 #include <dt-bindings/reset/amlogic,meson8b-reset.h>
11 #include "meson.dtsi"
12
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 71983 bytes --]
next prev parent reply other threads:[~2019-12-09 3:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-08 18:05 [PATCH 0/3] ARM: dts: meson: clock updates Martin Blumenstingl
2019-12-08 18:05 ` [PATCH 1/3] ARM: dts: meson: provide the XTAL clock using a fixed-clock Martin Blumenstingl
2019-12-08 18:05 ` [PATCH 2/3] ARM: dts: meson8: add the DDR clock controller Martin Blumenstingl
2019-12-09 3:20 ` kbuild test robot [this message]
2019-12-08 18:05 ` [PATCH 3/3] ARM: dts: meson8b: " Martin Blumenstingl
2019-12-12 15:48 ` [PATCH 0/3] ARM: dts: meson: clock updates Jerome Brunet
2019-12-13 22:34 ` Kevin Hilman
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=201912091038.s62HNGKV%lkp@intel.com \
--to=lkp@intel.com \
--cc=jbrunet@baylibre.com \
--cc=kbuild-all@lists.01.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.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