From: kbuild test robot <lkp@intel.com>
To: Lubomir Rintel <lkundrak@v3.sk>
Cc: kbuild-all@lists.01.org, Olof Johansson <olof@lixom.net>,
Arnd Bergmann <arnd@arndb.de>,
Kishon Vijay Abraham I <kishon@ti.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-clk@vger.kernel.org, soc@kernel.org,
Lubomir Rintel <lkundrak@v3.sk>
Subject: Re: [PATCH 4/5] ARM: dts: mmp3: Add HSIC controllers
Date: Mon, 23 Dec 2019 17:57:00 +0800 [thread overview]
Message-ID: <201912231750.0jrFNDq4%lkp@intel.com> (raw)
In-Reply-To: <20191220065314.237624-5-lkundrak@v3.sk>
[-- Attachment #1: Type: text/plain, Size: 1389 bytes --]
Hi Lubomir,
I love your patch! Yet something to improve:
[auto build test ERROR on robh/for-next]
[also build test ERROR on clk/clk-next phy/next arm-soc/for-next v5.5-rc3 next-20191220]
[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/Lubomir-Rintel/dt-bindings-marvell-mmp2-Add-clock-ids-for-the-HSIC-clocks/20191223-141100
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
config: arm-defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (GCC) 7.5.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.5.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/mmp3.dtsi:207.5-6 syntax error
FATAL ERROR: Unable to parse input tree
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 49450 bytes --]
next prev parent reply other threads:[~2019-12-23 9:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 6:53 [PATCH 1/5] Enable HSIC on MMP3 SoC Lubomir Rintel
2019-12-20 6:53 ` [PATCH 1/5] dt-bindings: marvell,mmp2: Add clock ids for the HSIC clocks Lubomir Rintel
2019-12-23 19:32 ` Stephen Boyd
2019-12-20 6:53 ` [PATCH 2/5] clk: mmp2: Add " Lubomir Rintel
2019-12-23 19:33 ` Stephen Boyd
2019-12-20 6:53 ` [PATCH 3/5] dt-bindings: phy: Add binding for marvell,mmp3-hsic-phy Lubomir Rintel
2020-01-07 22:20 ` Rob Herring
2019-12-20 6:53 ` [PATCH 4/5] ARM: dts: mmp3: Add HSIC controllers Lubomir Rintel
2019-12-20 7:05 ` Lubomir Rintel
2020-01-06 19:22 ` Olof Johansson
2019-12-23 9:57 ` kbuild test robot [this message]
2019-12-20 6:53 ` [PATCH 5/5] ARM: dts: mmp3-dell-ariel: Enable the HSIC Lubomir Rintel
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=201912231750.0jrFNDq4%lkp@intel.com \
--to=lkp@intel.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=kishon@ti.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=soc@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).