From: Heiko Stuebner <heiko@sntech.de>
To: kbuild test robot <lkp@intel.com>
Cc: Jacob Chen <jacob-chen@iotwrt.com>,
kbuild-all@01.org, linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
kever.yang@rock-chips.com, mark.yao@rock-chips.com,
zhangqing@rock-chips.com
Subject: Re: [PATCH 2/2] arm64: dts: rockchip: Add support for rk3399 excavator main board
Date: Sun, 06 Aug 2017 17:46:01 +0200 [thread overview]
Message-ID: <3974482.WU7faVNnLz@phil> (raw)
In-Reply-To: <201708040551.mSxlH21s%fengguang.wu@intel.com>
Am Freitag, 4. August 2017, 05:28:40 CEST schrieb kbuild test robot:
> Hi Jacob,
>
> [auto build test ERROR on rockchip/for-next]
> [also build test ERROR on v4.13-rc3 next-20170803]
> [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/Jacob-Chen/arm64-dts-rockchip-Add-support-for-rk3399-sapphire-SOM/20170804-002840
> base: https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git for-next
> config: arm64-defconfig (attached as .config)
> compiler: aarch64-linux-gnu-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
> # save the attached .config to linux build tree
> make.cross ARCH=arm64
>
> All errors (new ones prefixed by >>):
>
> >> Error: arch/arm64/boot/dts/rockchip/rk3399-sapphire.dtsi:197.1-6 Label or path hdmi not found
> >> Error: arch/arm64/boot/dts/rockchip/rk3399-sapphire.dtsi:632.1-6 Label or path vopb not found
> >> Error: arch/arm64/boot/dts/rockchip/rk3399-sapphire.dtsi:636.1-10 Label or path vopb_mmu not found
> >> Error: arch/arm64/boot/dts/rockchip/rk3399-sapphire.dtsi:640.1-6 Label or path vopl not found
> >> Error: arch/arm64/boot/dts/rockchip/rk3399-sapphire.dtsi:644.1-10 Label or path vopl_mmu not found
> >> Error: arch/arm64/boot/dts/rockchip/rk3399-sapphire-excavator.dts:157.1-5 Label or path edp not found
> FATAL ERROR: Syntax error parsing input tree
that's ok, it just depended on the series from Jacob adding these
display-related nodes and I've applied that series before picking up
this new board, so everything still compiles fine.
Heiko
next prev parent reply other threads:[~2017-08-06 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 10:32 [PATCH 1/2] arm64: dts: rockchip: Add support for rk3399 sapphire SOM Jacob Chen
2017-08-03 10:32 ` [PATCH 2/2] arm64: dts: rockchip: Add support for rk3399 excavator main board Jacob Chen
2017-08-03 21:28 ` kbuild test robot
2017-08-06 15:46 ` Heiko Stuebner [this message]
2017-08-06 15:44 ` Heiko Stuebner
[not found] ` <1501756357-10511-1-git-send-email-jacob-chen-fyOeoxGR3m/QT0dZR+AlfA@public.gmane.org>
2017-08-03 10:34 ` [PATCH 1/2] arm64: dts: rockchip: Add support for rk3399 sapphire SOM Jacob Chen
[not found] ` <CAFLEztQOD5rkDRyL9es4vkyFDX-S+WqVuVUH+q4N6YvSaKmoXw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-08-04 9:51 ` Jacob Chen
2017-08-06 15:41 ` Heiko Stuebner
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=3974482.WU7faVNnLz@phil \
--to=heiko@sntech.de \
--cc=devicetree@vger.kernel.org \
--cc=jacob-chen@iotwrt.com \
--cc=kbuild-all@01.org \
--cc=kever.yang@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=lkp@intel.com \
--cc=mark.yao@rock-chips.com \
--cc=zhangqing@rock-chips.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).