From: kbuild test robot <lkp@intel.com>
To: Harvey Hunt <harvey.hunt@imgtec.com>
Cc: kbuild-all@01.org, robh+dt@kernel.org, mark.rutland@arm.com,
ralf@linux-mips.org, john@phrozen.org,
Harvey Hunt <harvey.hunt@imgtec.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-mips@linux-mips.org
Subject: Re: [PATCH 1/2] MIPS: Add Onion Omega2+ board
Date: Fri, 18 Aug 2017 07:11:55 +0800 [thread overview]
Message-ID: <201708180751.df50Z3gA%fengguang.wu@intel.com> (raw)
In-Reply-To: <1502814945-41052-1-git-send-email-harvey.hunt@imgtec.com>
[-- Attachment #1: Type: text/plain, Size: 938 bytes --]
Hi Harvey,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.13-rc5 next-20170817]
[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/Harvey-Hunt/MIPS-Add-Onion-Omega2-board/20170818-033709
config: mips-maltaup_xpa_defconfig (attached as .config)
compiler: mipsel-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=mips
All errors (new ones prefixed by >>):
>> FATAL ERROR: Couldn't open "mt7628a.dtsi": No such file or directory
---
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: 18507 bytes --]
prev parent reply other threads:[~2017-08-17 23:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 16:35 Harvey Hunt
2017-08-15 16:35 ` [PATCH 2/2] MIPS: configs: Add Onion Omega2+ defconfig Harvey Hunt
2017-08-17 23:11 ` kbuild test robot [this message]
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=201708180751.df50Z3gA%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=harvey.hunt@imgtec.com \
--cc=john@phrozen.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mark.rutland@arm.com \
--cc=ralf@linux-mips.org \
--cc=robh+dt@kernel.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®