From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [rockchip:v4.14-armsoc/dts32 24/24] Error: arch/arm/boot/dts/rv1108.dtsi:166.18-19 syntax error
Date: Tue, 01 Aug 2017 20:52:34 +0200 [thread overview]
Message-ID: <5139664.u4Jz45l4se@phil> (raw)
In-Reply-To: <201708020247.iHTNS8tt%fengguang.wu@intel.com>
Am Mittwoch, 2. August 2017, 02:46:48 CEST schrieb kbuild test robot:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git v4.14-armsoc/dts32
> head: 752db55c894e48ff08a89946604950071bed5f1e
> commit: 752db55c894e48ff08a89946604950071bed5f1e [24/24] ARM: dts: rockchip: add watchdog dt node for rv1108
> config: arm-at91_dt_defconfig (attached as .config)
> compiler: arm-linux-gnueabi-gcc (Debian 6.1.1-9) 6.1.1 20160705
> reproduce:
> wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout 752db55c894e48ff08a89946604950071bed5f1e
> # save the attached .config to linux build tree
> make.cross ARCH=arm
>
> All errors (new ones prefixed by >>):
>
> >> Error: arch/arm/boot/dts/rv1108.dtsi:166.18-19 syntax error
> FATAL ERROR: Unable to parse input tree
Thanks for noticing. I blame it on the heat today, that I applied the
rv1108-watchdog patch without noticing the missing clock-id.
I'll drop it again, until the clock-id is present.
Heiko
prev parent reply other threads:[~2017-08-01 18:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 18:46 [rockchip:v4.14-armsoc/dts32 24/24] Error: arch/arm/boot/dts/rv1108.dtsi:166.18-19 syntax error kbuild test robot
2017-08-01 18:52 ` Heiko Stuebner [this message]
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=5139664.u4Jz45l4se@phil \
--to=heiko@sntech.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox