From: kbuild test robot <lkp@intel.com>
To: Scott Branden <scott.branden@broadcom.com>
Cc: kbuild-all@01.org, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Eric Anholt <eric@anholt.net>,
Stefan Wahren <stefan.wahren@i2se.com>,
BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org,
Scott Branden <scott.branden@broadcom.com>
Subject: Re: [PATCH 2/2] arm64: dts: move rpi into rpi directory
Date: Wed, 9 Aug 2017 06:39:47 +0800 [thread overview]
Message-ID: <201708090619.AOiafigN%fengguang.wu@intel.com> (raw)
In-Reply-To: <1500483950-9217-3-git-send-email-scott.branden@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 1523 bytes --]
Hi Scott,
[auto build test ERROR on v4.13-rc1]
[cannot apply to robh/for-next arm64/for-next/core next-20170808]
[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/Scott-Branden/arm64-dts-move-ns2-into-northstar2-directory/20170721-023618
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 >>):
>> arch/arm/boot/dts/bcm2837-rpi-3-b.dts:1:46: fatal error: arm64/broadcom/bcm2837-rpi-3-b.dts: No such file or directory
#include "arm64/broadcom/bcm2837-rpi-3-b.dts"
^
compilation terminated.
vim +1 arch/arm/boot/dts/bcm2837-rpi-3-b.dts
072f58af Eric Anholt 2017-04-25 @1 #include "arm64/broadcom/bcm2837-rpi-3-b.dts"
:::::: The code at line 1 was first introduced by commit
:::::: 072f58af1dfbc39f8daf6be170d90c2465df4771 ARM: dts: Add devicetree for the Raspberry Pi 3, for arm32 (v6)
:::::: TO: Eric Anholt <eric@anholt.net>
:::::: CC: Eric Anholt <eric@anholt.net>
---
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: 23094 bytes --]
next prev parent reply other threads:[~2017-08-08 22:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 17:05 [PATCH 0/2] arm64: dts: cleanup Broadcom boards per SoC Scott Branden
2017-07-19 17:05 ` [PATCH 1/2] arm64: dts: move ns2 into northstar2 directory Scott Branden
2017-07-28 23:31 ` Florian Fainelli
2017-07-19 17:05 ` [PATCH 2/2] arm64: dts: move rpi into rpi directory Scott Branden
2017-07-19 20:21 ` Eric Anholt
2017-07-19 20:25 ` Scott Branden
2017-08-08 22:39 ` kbuild test robot [this message]
2017-07-28 14:39 ` [PATCH 0/2] arm64: dts: cleanup Broadcom boards per SoC Scott Branden
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=201708090619.AOiafigN%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=scott.branden@broadcom.com \
--cc=stefan.wahren@i2se.com \
--cc=will.deacon@arm.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®