From: kbuild test robot <lkp@intel.com>
To: "Clément Péron" <peron.clem@gmail.com>
Cc: kbuild-all@01.org, "Colin Didier" <colin.didier@devialet.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Daniel Lezcano" <daniel.lezcano@linaro.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Fabio Estevam" <fabio.estevam@nxp.com>,
"Vladimir Zapolskiy" <vladimir_zapolskiy@mentor.com>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Rob Herring" <robh@kernel.org>,
"NXP Linux Team" <linux-imx@nxp.com>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Clément Peron" <clement.peron@devialet.com>
Subject: Re: [PATCH v5 4/4] ARM: dts: imx: add missing compatible and clock properties for EPIT
Date: Mon, 4 Jun 2018 22:57:30 +0800 [thread overview]
Message-ID: <201806042209.Muyb3cE5%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180604100035.19558-5-peron.clem@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]
Hi Colin,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on shawnguo/for-next]
[also build test ERROR on v4.17 next-20180601]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Cl-ment-P-ron/Reintroduce-i-MX-EPIT-Timer/20180604-211036
base: https://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git for-next
config: arm-realview_defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 7.2.0-11) 7.2.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
make.cross ARCH=arm
All errors (new ones prefixed by >>):
>> Error: arch/arm/boot/dts/imx6sl.dtsi:661.19-20 syntax error
FATAL ERROR: Unable to parse 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: 18007 bytes --]
next prev parent reply other threads:[~2018-06-04 15:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 10:00 [PATCH v5 0/4] Reintroduce i.MX EPIT Timer Clément Péron
2018-06-04 10:00 ` [PATCH v5 1/4] ARM: imx: remove inexistant EPIT timer init Clément Péron
2018-06-04 10:00 ` [PATCH v5 2/4] dt-bindings: timer: add i.MX EPIT timer binding Clément Péron
2018-06-05 15:23 ` Rob Herring
2018-06-06 8:12 ` Clément Péron
2018-06-04 10:00 ` [PATCH v5 3/4] clocksource: add driver for i.MX EPIT timer Clément Péron
2018-06-04 10:00 ` [PATCH v5 4/4] ARM: dts: imx: add missing compatible and clock properties for EPIT Clément Péron
2018-06-04 14:57 ` kbuild test robot [this message]
2018-06-05 2:10 ` kbuild test robot
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=201806042209.Muyb3cE5%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=clement.peron@devialet.com \
--cc=colin.didier@devialet.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=kbuild-all@01.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peron.clem@gmail.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=tglx@linutronix.de \
--cc=vladimir_zapolskiy@mentor.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).