From: lkp@intel.com (kbuild test robot)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH] ARM64: dts: meson-gx: Use correct mmc clock source 0
Date: Sun, 6 Aug 2017 13:25:21 +0800 [thread overview]
Message-ID: <201708061316.vyrWnnKm%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170731120552.31606-1-jbrunet@baylibre.com>
Hi Jerome,
[auto build test ERROR on robh/for-next]
[also build test ERROR on v4.13-rc3 next-20170804]
[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/Jerome-Brunet/ARM64-dts-meson-gx-Use-correct-mmc-clock-source-0/20170801-002221
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
config: arm64-allyesconfig (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/amlogic/meson-gxbb.dtsi:655.11-12 syntax error
FATAL ERROR: Unable to parse input tree
--
>> Error: arch/arm64/boot/dts/amlogic/meson-gxl.dtsi:596.11-12 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config.gz
Type: application/gzip
Size: 56922 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-amlogic/attachments/20170806/127e1b70/attachment.gz>
prev parent reply other threads:[~2017-08-06 5:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 12:05 Jerome Brunet
2017-08-01 19:48 ` Kevin Hilman
2017-08-06 5:25 ` 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=201708061316.vyrWnnKm%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=linus-amlogic@lists.infradead.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®