mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: James Pettigrew <james@innovum.com.au>
Cc: kbuild-all@01.org, maxime.ripard@free-electrons.com,
	robh+dt@kernel.com, mark.rutland@arm.com, linux@armlinux.org.uk,
	wens@csie.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com,
	james@innovum.com.au
Subject: Re: [PATCH v2] ARM: dts: sun8i: Add dts file for the NanoPi NEO SBC
Date: Mon, 5 Sep 2016 10:35:54 +0800	[thread overview]
Message-ID: <201609051025.IbTHt9ri%fengguang.wu@intel.com> (raw)
In-Reply-To: <1473036168-20933-1-git-send-email-james@innovum.com.au>

[-- Attachment #1: Type: text/plain, Size: 1384 bytes --]

Hi James,

[auto build test ERROR on mripard/sunxi/for-next]
[also build test ERROR on v4.8-rc5 next-20160825]
[cannot apply to robh/for-next]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
[Suggest to use git(>=2.9.0) format-patch --base=<commit> (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on]
[Check https://git-scm.com/docs/git-format-patch for more information]

url:    https://github.com/0day-ci/linux/commits/James-Pettigrew/ARM-dts-sun8i-Add-dts-file-for-the-NanoPi-NEO-SBC/20160905-085509
base:   https://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git sunxi/for-next
config: arm-aspeed_g5_defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 5.4.0-6) 5.4.0 20160609
reproduce:
        wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/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/sun8i-h3-nanopi-neo.dts:65.21-22 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

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 7654 bytes --]

  reply	other threads:[~2016-09-05  2:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-01  3:48 [PATCH 1/1] " james
2016-09-04 20:13 ` Rask Ingemann Lambertsen
2016-09-05  0:42 ` [PATCH v2] " James Pettigrew
2016-09-05  2:35   ` kbuild test robot [this message]
2016-09-05  4:31 ` [PATCH v3] " James Pettigrew
2016-09-05 12:06   ` Maxime Ripard
2016-09-05 18:31   ` Rask Ingemann Lambertsen
2016-09-05 22:15 ` [PATCH v4 0/2] ARM: sunxi: Add support for FriendlyARM " James Pettigrew
2016-09-05 22:15   ` [PATCH v4 1/2] ARM: dts: sun8i: Add dts file for the " James Pettigrew
2016-09-05 22:15   ` [PATCH v4 2/2] devicetree: Add vendor prefix for FriendlyARM James Pettigrew
2016-09-06  2:41     ` [linux-sunxi] " Chen-Yu Tsai
2016-09-06  6:41   ` [PATCH v4 0/2] ARM: sunxi: Add support for FriendlyARM NanoPi NEO SBC Maxime Ripard

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=201609051025.IbTHt9ri%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=james@innovum.com.au \
    --cc=kbuild-all@01.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@googlegroups.com \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=maxime.ripard@free-electrons.com \
    --cc=robh+dt@kernel.com \
    --cc=wens@csie.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

all inboxes | Powered by JetHome®