From: kernel test robot <lkp@intel.com>
To: Sudeep Holla <sudeep.holla@arm.com>,
Linus Walleij <linus.walleij@linaro.org>
Cc: kbuild-all@lists.01.org, Sudeep Holla <sudeep.holla@arm.com>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] ARM: dts: versatile: Fix up interrupt controller node names
Date: Thu, 1 Jul 2021 18:53:53 +0800 [thread overview]
Message-ID: <202107011848.TwF0sgSM-lkp@intel.com> (raw)
In-Reply-To: <20210617210825.3064367-1-sudeep.holla@arm.com>
[-- Attachment #1: Type: text/plain, Size: 1875 bytes --]
Hi Sudeep,
I love your patch! Yet something to improve:
[auto build test ERROR on robh/for-next]
[also build test ERROR on pinctrl/devel v5.13 next-20210630]
[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/Sudeep-Holla/ARM-dts-versatile-Fix-up-interrupt-controller-node-names/20210618-050956
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) 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/39c2a1b84ddd856b2a8015abc7952b9ca79a5c4c
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Sudeep-Holla/ARM-dts-versatile-Fix-up-interrupt-controller-node-names/20210618-050956
git checkout 39c2a1b84ddd856b2a8015abc7952b9ca79a5c4c
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross O=build_dir ARCH=arm SHELL=/bin/bash
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 >>):
arch/arm/boot/dts/versatile-pb.dts:10.22-17.5: ERROR (duplicate_label): /amba/intc@10003000: Duplicate label 'sic' on /amba/intc@10003000 and /amba/interrupt-controller@10003000
>> ERROR: Input tree has errors, aborting (use -f to force output)
---
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: 79104 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH 1/2] ARM: dts: versatile: Fix up interrupt controller node names
Date: Thu, 01 Jul 2021 18:53:53 +0800 [thread overview]
Message-ID: <202107011848.TwF0sgSM-lkp@intel.com> (raw)
In-Reply-To: <20210617210825.3064367-1-sudeep.holla@arm.com>
[-- Attachment #1: Type: text/plain, Size: 1919 bytes --]
Hi Sudeep,
I love your patch! Yet something to improve:
[auto build test ERROR on robh/for-next]
[also build test ERROR on pinctrl/devel v5.13 next-20210630]
[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/Sudeep-Holla/ARM-dts-versatile-Fix-up-interrupt-controller-node-names/20210618-050956
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) 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/39c2a1b84ddd856b2a8015abc7952b9ca79a5c4c
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Sudeep-Holla/ARM-dts-versatile-Fix-up-interrupt-controller-node-names/20210618-050956
git checkout 39c2a1b84ddd856b2a8015abc7952b9ca79a5c4c
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross O=build_dir ARCH=arm SHELL=/bin/bash
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 >>):
arch/arm/boot/dts/versatile-pb.dts:10.22-17.5: ERROR (duplicate_label): /amba/intc(a)10003000: Duplicate label 'sic' on /amba/intc(a)10003000 and /amba/interrupt-controller(a)10003000
>> ERROR: Input tree has errors, aborting (use -f to force output)
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 79104 bytes --]
next prev parent reply other threads:[~2021-07-01 10:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 21:08 [PATCH 1/2] ARM: dts: versatile: Fix up interrupt controller node names Sudeep Holla
2021-06-17 21:08 ` [PATCH 2/2] ARM: dts: nomadik: " Sudeep Holla
2021-06-26 0:01 ` Linus Walleij
2021-06-26 0:00 ` [PATCH 1/2] ARM: dts: versatile: " Linus Walleij
2021-07-01 10:53 ` kernel test robot [this message]
2021-07-01 10:53 ` kernel test robot
2021-07-01 13:05 ` Sudeep Holla
2021-07-01 13:05 ` Sudeep Holla
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=202107011848.TwF0sgSM-lkp@intel.com \
--to=lkp@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linus.walleij@linaro.org \
--cc=robh+dt@kernel.org \
--cc=sudeep.holla@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.