From: kernel test robot <lkp@intel.com>
To: "Drew Fustini" <drew@beagleboard.org>,
"Tony Lindgren" <tony@atomide.com>,
"Rob Herring" <robh+dt@kernel.org>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
"Linus Walleij" <linus.walleij@linaro.org>,
"Haojian Zhuang" <haojian.zhuang@linaro.org>,
devicetree@vger.kernel.org,
"Benoît Cousson" <bcousson@baylibre.com>
Cc: kbuild-all@lists.01.org
Subject: Re: [PATCH 1/3] ARM: dts: change AM33XX_PADCONF macro separate conf and mux
Date: Fri, 19 Jun 2020 08:50:13 +0800 [thread overview]
Message-ID: <202006190818.fgvRcvF0%lkp@intel.com> (raw)
In-Reply-To: <20200618125057.41252-2-drew@beagleboard.org>
[-- Attachment #1: Type: text/plain, Size: 2508 bytes --]
Hi Drew,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on robh/for-next]
[also build test ERROR on omap/for-next pinctrl/devel v5.8-rc1 next-20200618]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Drew-Fustini/pinctrl-single-support-pinctrl-cells-2/20200618-205624
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
config: arm-allyesconfig (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
# 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/am335x-baltos.dtsi:53.39-40 syntax error
FATAL ERROR: Unable to parse input tree
--
>> Error: arch/arm/boot/dts/am335x-igep0033.dtsi:57.39-40 syntax error
FATAL ERROR: Unable to parse input tree
--
>> Error: arch/arm/boot/dts/am335x-bone-common.dtsi:71.39-40 syntax error
FATAL ERROR: Unable to parse input tree
--
>> Error: arch/arm/boot/dts/am335x-osd335x-common.dtsi:39.39-40 syntax error
FATAL ERROR: Unable to parse input tree
--
>> Error: arch/arm/boot/dts/am335x-chilisom.dtsi:30.39-40 syntax error
FATAL ERROR: Unable to parse input tree
--
>> Error: arch/arm/boot/dts/am335x-cm-t335.dts:93.39-40 syntax error
FATAL ERROR: Unable to parse input tree
--
>> Error: arch/arm/boot/dts/am335x-evm.dts:170.39-40 syntax error
FATAL ERROR: Unable to parse input tree
--
>> Error: arch/arm/boot/dts/am335x-evmsk.dts:207.39-40 syntax error
FATAL ERROR: Unable to parse input tree
--
>> Error: arch/arm/boot/dts/am335x-icev2.dts:157.39-40 syntax error
FATAL ERROR: Unable to parse input tree
--
>> Error: arch/arm/boot/dts/am335x-lxm.dts:46.39-40 syntax error
FATAL ERROR: Unable to parse input tree
--
>> Error: arch/arm/boot/dts/am335x-moxa-uc-2100-common.dtsi:36.39-40 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: 75664 bytes --]
next prev parent reply other threads:[~2020-06-19 0:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 12:50 [PATCH 0/3] pinctrl: single: support #pinctrl-cells = 2 Drew Fustini
2020-06-18 12:50 ` [PATCH 1/3] ARM: dts: change AM33XX_PADCONF macro separate conf and mux Drew Fustini
2020-06-19 0:50 ` kernel test robot [this message]
2020-06-18 12:50 ` [PATCH 2/3] ARM: dts: am33xx-l4: change #pinctrl-cells from 1 to 2 Drew Fustini
2020-06-18 12:50 ` [PATCH 3/3] pinctrl: single: parse #pinctrl-cells = 2 Drew Fustini
2020-06-22 16:11 ` [PATCH 0/3] pinctrl: single: support " Tony Lindgren
2020-06-22 16:46 ` Drew Fustini
2020-06-22 16:48 ` Tony Lindgren
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=202006190818.fgvRcvF0%lkp@intel.com \
--to=lkp@intel.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=drew@beagleboard.org \
--cc=haojian.zhuang@linaro.org \
--cc=kbuild-all@lists.01.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.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).