From: xiaolong.ye@intel.com (Ye Xiaolong)
To: linux-arm-kernel@lists.infradead.org
Subject: [kbuild-all] [PATCH 3/3] ARM: dts: iwg20m: Add MMCIF0 support
Date: Thu, 13 Jul 2017 16:46:00 +0800 [thread overview]
Message-ID: <20170713084600.GA1787@yexl-desktop> (raw)
In-Reply-To: <20170713075414.GF5580@verge.net.au>
On 07/13, Simon Horman wrote:
>On Thu, Jul 13, 2017 at 08:25:56AM +0800, kbuild test robot wrote:
>> Hi Chris,
>>
>> [auto build test ERROR on renesas/next]
>> [also build test ERROR on next-20170712]
>> [cannot apply to v4.12]
>> [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/Chris-Paterson/Add-MMCIF0-support-for-r8a7743-iwg20m/20170713-042814
>> base: https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git next
>> 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 >>):
>>
>> >> Error: arch/arm/boot/dts/r8a7743-iwg20m.dtsi:40.1-5 Label or path pfc not found
>> FATAL ERROR: Syntax error parsing input tree
>
>This seems to be a false positive. The node in question is present in
>the devel branch which is the base of these changes.
Thanks for the feedback, we'll update 0day's configuration accordingly.
Thanks,
Xiaolong
>
>
>_______________________________________________
>kbuild-all mailing list
>kbuild-all at lists.01.org
>https://lists.01.org/mailman/listinfo/kbuild-all
next prev parent reply other threads:[~2017-07-13 8:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 10:03 [PATCH 0/3] Add MMCIF0 support for r8a7743/iwg20m Chris Paterson
2017-07-12 10:03 ` [PATCH 1/3] dt-bindings: mmc: sh_mmcif: Document r8a7743 DT bindings Chris Paterson
2017-07-12 11:20 ` Geert Uytterhoeven
2017-07-13 7:54 ` Simon Horman
2017-07-13 8:00 ` Geert Uytterhoeven
2017-07-13 8:07 ` Simon Horman
2017-07-13 10:06 ` Ulf Hansson
2017-07-12 10:03 ` [PATCH 2/3] ARM: dts: r8a7743: Add MMCIF0 support Chris Paterson
2017-07-12 11:21 ` Geert Uytterhoeven
2017-07-13 7:59 ` Simon Horman
2017-07-12 10:03 ` [PATCH 3/3] ARM: dts: iwg20m: " Chris Paterson
2017-07-12 11:52 ` Geert Uytterhoeven
2017-07-13 8:02 ` Simon Horman
2017-07-13 8:12 ` Simon Horman
2017-07-13 9:28 ` Chris Paterson
2017-07-13 0:25 ` kbuild test robot
2017-07-13 7:54 ` Simon Horman
2017-07-13 8:46 ` Ye Xiaolong [this message]
2017-07-13 15:39 ` [PATCH v2] " Chris Paterson
2017-07-13 16:31 ` Geert Uytterhoeven
2017-07-14 7:33 ` Simon Horman
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=20170713084600.GA1787@yexl-desktop \
--to=xiaolong.ye@intel.com \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).