From: Matthias Brugger <matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: kbuild test robot <lkp-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org
Cc: kbuild-all-JC7UmRfGjtg@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
john-Pj+rj9U5foFAfugRpC6u6w@public.gmane.org,
linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v4 3/9] arm: dts: mt7623: add mt7623-mt6323.dtsi file
Date: Mon, 29 May 2017 17:27:45 +0200 [thread overview]
Message-ID: <d565b4dd-f6b7-ee43-ddfe-ae98328646ed@gmail.com> (raw)
In-Reply-To: <201705281908.LU8TFOQ8%fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
On 28/05/17 13:31, kbuild test robot wrote:
> Hi John,
>
> [auto build test ERROR on robh/for-next]
> [also build test ERROR on v4.12-rc2 next-20170526]
> [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/sean-wang-mediatek-com/arm-dts-extend-mt7623-support/20170525-142103
> base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
Mediatek dts patches should be tested against:
https://github.com/mbgg/linux-mediatek.git for-next
Not sure why this happend, as this got already fixed in lkp-tests:
bc0c8847 ("mediatek: mark for-next branch")
Regards,
Matthias
> config: arm-allyesconfig (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/mt7623-mt6323.dtsi:33.1-7 Label or path pwrap not found
>>> Error: arch/arm/boot/dts/mt7623-mt6323.dtsi:261.1-6 Label or path mmc0 not found
>>> Error: arch/arm/boot/dts/mt7623-mt6323.dtsi:266.1-6 Label or path mmc1 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
>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-05-29 15:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 4:02 [PATCH v4 0/9] arm: dts: extend mt7623 support sean.wang
2017-05-25 4:02 ` [PATCH v4 1/9] dt-bindings: arm: mediatek: update for MT7623n SoC and relevant boards sean.wang
2017-05-31 17:54 ` Rob Herring
2017-05-25 4:02 ` [PATCH v4 3/9] arm: dts: mt7623: add mt7623-mt6323.dtsi file sean.wang
[not found] ` <2c770301279b10b78382b53529a6b83a6d847e32.1495683769.git.sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-05-28 11:31 ` kbuild test robot
[not found] ` <201705281908.LU8TFOQ8%fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-05-29 15:27 ` Matthias Brugger [this message]
[not found] ` <d565b4dd-f6b7-ee43-ddfe-ae98328646ed-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-05-31 8:08 ` [kbuild-all] " Ye Xiaolong
2017-05-25 4:02 ` [PATCH v4 5/9] ARM: mediatek: add MT7623a smp bringup code sean.wang
[not found] ` <cover.1495683769.git.sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-05-25 4:02 ` [PATCH v4 2/9] dt-bindings: arm: mediatek: add bindings for mediatek MT7623a SoC Platform sean.wang-NuS5LvNUpcJWk0Htik3J/w
2017-05-25 4:02 ` [PATCH v4 4/9] arm: dts: mt7623: rename mt7623-evb.dts to arch/arm/boot/dts/mt7623n-rfb.dtsi sean.wang-NuS5LvNUpcJWk0Htik3J/w
2017-05-25 4:02 ` [PATCH v4 6/9] arm: dts: mt7623: cleanup the mt7623n rfb uart nodes sean.wang-NuS5LvNUpcJWk0Htik3J/w
2017-05-25 4:02 ` [PATCH v4 7/9] arm: dts: mt7623: enable the usb device on the mt7623n rfb sean.wang-NuS5LvNUpcJWk0Htik3J/w
[not found] ` <4cb528c77f4d44bd0932b69f39b0d5b557d9eab1.1495683769.git.sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-05-28 16:02 ` kbuild test robot
2017-05-25 4:02 ` [PATCH v4 9/9] arm: dts: mt7623: add dts file for Bananapi R2 (BPI-R2) board sean.wang-NuS5LvNUpcJWk0Htik3J/w
[not found] ` <5cc5489b38fc2723c30c8cfe0d4353f967d100f3.1495683769.git.sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-05-28 20:53 ` kbuild test robot
2017-07-27 14:39 ` Matthias Brugger
[not found] ` <805ad5c4-db47-ef10-565d-b63e33a84bdf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-07-31 2:46 ` Sean Wang
2017-05-25 4:02 ` [PATCH v4 8/9] arm: dts: mt7623: enable the nand device on the mt7623n nand rfb sean.wang
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=d565b4dd-f6b7-ee43-ddfe-ae98328646ed@gmail.com \
--to=matthias.bgg-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=john-Pj+rj9U5foFAfugRpC6u6w@public.gmane.org \
--cc=kbuild-all-JC7UmRfGjtg@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=lkp-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.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).