From: kernel test robot <lkp@intel.com>
To: "Cristian Ciocaltea" <cristian.ciocaltea@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Andreas Färber" <afaerber@suse.de>,
"Manivannan Sadhasivam" <mani@kernel.org>
Cc: kbuild-all@lists.01.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-actions@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] ARM: dts: owl-s500: Add ethernet support
Date: Wed, 16 Jun 2021 21:30:13 +0800 [thread overview]
Message-ID: <202106162101.RfHWePKS-lkp@intel.com> (raw)
In-Reply-To: <222ee0c2cb431619f558dce9726585ac92f65e00.1623401998.git.cristian.ciocaltea@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1682 bytes --]
Hi Cristian,
I love your patch! Yet something to improve:
[auto build test ERROR on robh/for-next]
[also build test ERROR on v5.13-rc6 next-20210615]
[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/Cristian-Ciocaltea/Add-Ethernet-DTS-for-Actions-Semi-Owl-S500-SoCs/20210616-121106
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
config: arm-randconfig-r025-20210615 (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/87e17f86112592e0805d0a081914f7b2eeb2770d
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Cristian-Ciocaltea/Add-Ethernet-DTS-for-Actions-Semi-Owl-S500-SoCs/20210616-121106
git checkout 87e17f86112592e0805d0a081914f7b2eeb2770d
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm
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 >>):
>> Error: arch/arm/boot/dts/owl-s500.dtsi:332.19-20 syntax error
>> FATAL ERROR: Unable to parse input tree
---
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: 30716 bytes --]
next prev parent reply other threads:[~2021-06-16 13:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 9:11 [PATCH v2 0/2] Add Ethernet DTS for Actions Semi Owl S500 SoCs Cristian Ciocaltea
2021-06-11 9:11 ` [PATCH v2 1/2] ARM: dts: owl-s500: Add ethernet support Cristian Ciocaltea
2021-06-16 13:30 ` kernel test robot [this message]
2021-06-28 6:22 ` Manivannan Sadhasivam
2021-06-28 7:02 ` Cristian Ciocaltea
2021-06-28 7:31 ` Manivannan Sadhasivam
2021-06-11 9:11 ` [PATCH v2 2/2] ARM: dts: owl-s500-roseapplepi: " Cristian Ciocaltea
2021-06-14 11:27 ` Manivannan Sadhasivam
2021-06-14 11:28 ` [PATCH v2 0/2] Add Ethernet DTS for Actions Semi Owl S500 SoCs Manivannan Sadhasivam
2021-06-14 12:11 ` Cristian Ciocaltea
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=202106162101.RfHWePKS-lkp@intel.com \
--to=lkp@intel.com \
--cc=afaerber@suse.de \
--cc=cristian.ciocaltea@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-actions@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=robh+dt@kernel.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).