From: kbuild test robot <lkp@intel.com>
To: "Andrew F. Davis" <afd@ti.com>
Cc: kbuild-all@01.org, "Benoît Cousson" <bcousson@baylibre.com>,
"Tony Lindgren" <tony@atomide.com>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
"Andrew F . Davis" <afd@ti.com>
Subject: Re: [PATCH] ARM: dts: am43xx-epos-evm: Enable SGX on EPOS boards
Date: Wed, 20 Sep 2017 18:15:00 +0800 [thread overview]
Message-ID: <201709201857.cwX7dK3r%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170918173130.17657-1-afd@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]
Hi Yogesh,
[auto build test ERROR on robh/for-next]
[also build test ERROR on v4.14-rc1 next-20170920]
[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/Andrew-F-Davis/ARM-dts-am43xx-epos-evm-Enable-SGX-on-EPOS-boards/20170920-154002
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
config: arm-s3c6400_defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
wget https://raw.githubusercontent.com/intel/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/am43x-epos-evm.dts:800.1-5 Label or path sgx not found
>> FATAL ERROR: Syntax error parsing 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: 16908 bytes --]
next prev parent reply other threads:[~2017-09-20 10:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 17:31 Andrew F. Davis
2017-09-20 10:15 ` kbuild test robot [this message]
2017-09-20 15:15 ` Andrew F. Davis
2017-10-02 14:52 ` Tony Lindgren
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=201709201857.cwX7dK3r%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=afd@ti.com \
--cc=bcousson@baylibre.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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®