From: kbuild test robot <lkp@intel.com>
To: Kamel Bouhara <kamel.bouhara@bootlin.com>
Cc: kbuild-all@lists.01.org, "Rob Herring" <robh+dt@kernel.org>,
"Nicolas Ferre" <nicolas.ferre@microchip.com>,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
"Ludovic Desroches" <ludovic.desroches@microchip.com>,
linux-arm-kernel@lists.infradead.org,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
"Kamel Bouhara" <kamel.bouhara@bootlin.com>,
"Kévin RAYMOND" <k.raymond@overkiz.com>,
"Mickael GARDET" <m.gardet@overkiz.com>
Subject: Re: [PATCH 3/3] ARM: at91: add Overkiz KIZBOX3 board
Date: Mon, 14 Oct 2019 12:49:01 +0800 [thread overview]
Message-ID: <201910141247.b3XxUBpr%lkp@intel.com> (raw)
In-Reply-To: <20191011125022.16329-4-kamel.bouhara@bootlin.com>
[-- Attachment #1: Type: text/plain, Size: 1353 bytes --]
Hi Kamel,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on robh/for-next]
[cannot apply to v5.4-rc3 next-20191011]
[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/Kamel-Bouhara/Add-new-Overkiz-Kizbox3-support/20191014-054232
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.4.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.4.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 >>):
>> Error: arch/arm/boot/dts/at91-kizbox3_common.dtsi:155.1-5 Label or path rtc not found
FATAL ERROR: Syntax error parsing input tree
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 71975 bytes --]
next prev parent reply other threads:[~2019-10-14 4:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 12:50 [PATCH 0/3] Add new Overkiz Kizbox3 support Kamel Bouhara
2019-10-11 12:50 ` [PATCH 1/3] dt-bindings: Add vendor prefix for Overkiz SAS Kamel Bouhara
2019-10-15 22:46 ` Rob Herring
2019-10-11 12:50 ` [PATCH 2/3] dt-bindings: arm: at91: Document Kizbox3 HS board binding Kamel Bouhara
2019-10-15 22:47 ` Rob Herring
2019-10-11 12:50 ` [PATCH 3/3] ARM: at91: add Overkiz KIZBOX3 board Kamel Bouhara
2019-10-14 4:49 ` kbuild test robot [this message]
2019-10-16 8:08 ` [PATCH 0/3] Add new Overkiz Kizbox3 support Alexandre Belloni
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=201910141247.b3XxUBpr%lkp@intel.com \
--to=lkp@intel.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=k.raymond@overkiz.com \
--cc=kamel.bouhara@bootlin.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=m.gardet@overkiz.com \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@bootlin.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).