mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Bu Tao <butao@hisilicon.com>
Cc: kbuild-all@01.org, robh+dt@kernel.org, mark.rutland@arm.com,
	xuwei5@hisilicon.com, catalin.marinas@arm.com,
	will.deacon@arm.com, vinholikatti@gmail.com,
	jejb@linux.vnet.ibm.com, martin.petersen@oracle.com,
	khilman@baylibre.com, arnd@arndb.de,
	gregory.clement@free-electrons.com,
	thomas.petazzoni@free-electrons.com,
	yamada.masahiro@socionext.com, riku.voipio@linaro.org,
	treding@nvidia.com, krzk@kernel.org, eric@anholt.net,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-scsi@vger.kernel.org,
	guodong.xu@linaro.org, suzhuangluan@hisilicon.com,
	kongfei@hisilicon.com, butao@hisilicon.com
Subject: Re: [PATCH v2 3/5] arm64: dts: Add ufs dts node
Date: Sun, 18 Jun 2017 08:31:19 +0800	[thread overview]
Message-ID: <201706180814.Kte2462z%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170616065119.10704-4-butao@hisilicon.com>

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

Hi Bu,

[auto build test ERROR on mkp-scsi/for-next]
[also build test ERROR on v4.12-rc5 next-20170616]
[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]

url:    https://github.com/0day-ci/linux/commits/Bu-Tao/scsi-ufs-add-ufs-driver-code-for-Hi3660-SoC/20170618-045141
base:   https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.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/hisilicon/hi3660.dtsi:152.24-25 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/gzip, Size: 35380 bytes --]

  reply	other threads:[~2017-06-18  0:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-16  6:51 [PATCH v2 0/5] scsi: ufs: add ufs driver code for Hi3660 SoC Bu Tao
2017-06-16  6:51 ` [PATCH v2 1/5] scsi: ufs: add hi3660 ufs driver code Bu Tao
2017-06-16  6:51 ` [PATCH v2 2/5] dt-bindings: scsi: ufs: add document for hi3660-ufs Bu Tao
2017-06-16 21:51   ` Arnd Bergmann
2017-06-22 11:44     ` Bu Tao
2017-06-22 11:51       ` Arnd Bergmann
2017-06-22 11:58         ` Bu Tao
2017-06-22 12:15           ` Arnd Bergmann
2017-06-22 12:23             ` Bu Tao
2017-06-23  1:05         ` Subhash Jadavani
2017-06-23  1:09           ` Bu Tao
2017-06-16  6:51 ` [PATCH v2 3/5] arm64: dts: Add ufs dts node Bu Tao
2017-06-18  0:31   ` kbuild test robot [this message]
2017-06-18  7:06     ` Guodong Xu
2017-06-16  6:51 ` [PATCH v2 4/5] arm64: defconfig: enable configs for hi3660 ufs Bu Tao
2017-06-16  6:51 ` [PATCH v2 5/5] arm64: defconfig: enable f2fs and squashfs Bu Tao

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=201706180814.Kte2462z%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=arnd@arndb.de \
    --cc=butao@hisilicon.com \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=eric@anholt.net \
    --cc=gregory.clement@free-electrons.com \
    --cc=guodong.xu@linaro.org \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=kbuild-all@01.org \
    --cc=khilman@baylibre.com \
    --cc=kongfei@hisilicon.com \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=martin.petersen@oracle.com \
    --cc=riku.voipio@linaro.org \
    --cc=robh+dt@kernel.org \
    --cc=suzhuangluan@hisilicon.com \
    --cc=thomas.petazzoni@free-electrons.com \
    --cc=treding@nvidia.com \
    --cc=vinholikatti@gmail.com \
    --cc=will.deacon@arm.com \
    --cc=xuwei5@hisilicon.com \
    --cc=yamada.masahiro@socionext.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

all inboxes | Powered by JetHome®