public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Frank Wang <frank.wang@rock-chips.com>
To: kbuild test robot <lkp@intel.com>, heiko@sntech.de
Cc: kbuild-all@01.org, robh+dt@kernel.org, mark.rutland@arm.com,
	linux@armlinux.org.uk, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, charles.chen@rock-chips.com,
	cody.xie@rock-chips.com, kevan.lan@rock-chips.com,
	huangtao@rock-chips.com, sugar.zhang@rock-chips.com,
	wmc@rock-chips.com
Subject: Re: [PATCH 3/3] arm: dts: rk322x: add watchdog device node.
Date: Thu, 18 May 2017 11:58:04 +0800	[thread overview]
Message-ID: <e39599a2-479a-11c3-a349-3c5a51fa130d@rock-chips.com> (raw)
In-Reply-To: <201705181148.b4AgD8sU%fengguang.wu@intel.com>

Hi,

Sorry, I forgot to declare that this change required below patch on 
patchwork.
https://patchwork.kernel.org/patch/9703945/


BR.
Frank

On 2017/5/18 11:18, kbuild test robot wrote:
> Hi Frank,
>
> [auto build test ERROR on rockchip/for-next]
> [also build test ERROR on v4.12-rc1 next-20170517]
> [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/Frank-Wang/add-and-fix-some-device-node-for-rk322x-SoC/20170518-081958
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git for-next
> 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
>          # save the attached .config to linux build tree
>          make.cross ARCH=arm
>
> All errors (new ones prefixed by >>):
>
>>> Error: arch/arm/boot/dts/rk322x.dtsi:286.18-19 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

  reply	other threads:[~2017-05-18  3:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-17  3:40 [PATCH 0/3] add and fix some device node for rk322x SoC Frank Wang
2017-05-17  3:40 ` [PATCH 1/3] arm: dts: rk322x: fix i2s1 pinctrl error Frank Wang
     [not found]   ` <1494992451-32542-2-git-send-email-frank.wang-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-05-17  9:01     ` Heiko Stübner
2017-05-17  9:21       ` Frank Wang
     [not found] ` <1494992451-32542-1-git-send-email-frank.wang-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-05-17  3:40   ` [PATCH 2/3] arm: dts: rk322x: correct uart2 pinctrl and add another sets Frank Wang
2017-05-17  6:31     ` Kever Yang
     [not found]       ` <3974d438-89ca-04e2-03cd-6d3946dd461e-9Onoh4P/yGk@public.gmane.org>
2017-05-17  7:35         ` Frank Wang
2017-05-17  3:40 ` [PATCH 3/3] arm: dts: rk322x: add watchdog device node Frank Wang
     [not found]   ` <1494992451-32542-4-git-send-email-frank.wang-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-05-18  3:18     ` kbuild test robot
2017-05-18  3:58       ` Frank Wang [this message]
2017-05-18  7:18         ` Heiko Stübner

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=e39599a2-479a-11c3-a349-3c5a51fa130d@rock-chips.com \
    --to=frank.wang@rock-chips.com \
    --cc=charles.chen@rock-chips.com \
    --cc=cody.xie@rock-chips.com \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=huangtao@rock-chips.com \
    --cc=kbuild-all@01.org \
    --cc=kevan.lan@rock-chips.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=lkp@intel.com \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sugar.zhang@rock-chips.com \
    --cc=wmc@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