From: rasmus.villemoes@prevas.dk (Rasmus Villemoes)
To: linux-arm-kernel@lists.infradead.org
Subject: [shawnguo:imx/dt 1/42] Error: arch/arm/boot/dts/ls1021a-moxa-uc-8410a.dts:19.1-2 syntax error
Date: Mon, 12 Feb 2018 08:55:41 +0100 [thread overview]
Message-ID: <bdfa3a5f-a942-374d-acfb-2cd7e8bde8ff@prevas.dk> (raw)
In-Reply-To: <201802121532.20rd85VM%fengguang.wu@intel.com>
On 2018-02-12 08:42, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git imx/dt
> head: 4ce917f8d003453415200c6be13b74ba4676ddeb
> commit: d287e28b2c909bf99a4aac5eb98521247b476517 [1/42] ARM: dts: ls1021a: add nodes for on-chip ram
> config: arm-at91_dt_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
> git checkout d287e28b2c909bf99a4aac5eb98521247b476517
> # save the attached .config to linux build tree
> make.cross ARCH=arm
>
> All errors (new ones prefixed by >>):
>
>>> Error: arch/arm/boot/dts/ls1021a-moxa-uc-8410a.dts:19.1-2 syntax error
>>> FATAL ERROR: Unable to parse input tree
> --
>>> Error: arch/arm/boot/dts/ls1021a-qds.dts:51.1-2 syntax error
>>> FATAL ERROR: Unable to parse input tree
> --
>>> Error: arch/arm/boot/dts/ls1021a-twr.dts:51.1-2 syntax error
>>> FATAL ERROR: Unable to parse input tree
Seems to be a rebase-induced error. The can3 node in imx/dt has lost its
closing brace.
Rasmus
next prev parent reply other threads:[~2018-02-12 7:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 7:42 [shawnguo:imx/dt 1/42] Error: arch/arm/boot/dts/ls1021a-moxa-uc-8410a.dts:19.1-2 syntax error kbuild test robot
2018-02-12 7:55 ` Rasmus Villemoes [this message]
2018-02-12 13:21 ` Shawn Guo
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=bdfa3a5f-a942-374d-acfb-2cd7e8bde8ff@prevas.dk \
--to=rasmus.villemoes@prevas.dk \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.