From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
To: "lkp@intel.com" <lkp@intel.com>
Cc: "mark.rutland@arm.com" <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"gnurou@gmail.com" <gnurou@gmail.com>,
"swarren@wwwdotorg.org" <swarren@wwwdotorg.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
"kbuild-all@01.org" <kbuild-all@01.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 1/3] arm: tegra: initial support for apalis tk1
Date: Sun, 26 Jun 2016 20:09:16 +0000 [thread overview]
Message-ID: <1466971755.3308.3.camel@toradex.com> (raw)
In-Reply-To: <201606261116.9IwjfA6i%fengguang.wu@intel.com>
On Sun, 2016-06-26 at 11:52 +0800, kbuild test robot wrote:
> Hi,
>
> [auto build test ERROR on robh/for-next]
> [also build test ERROR on v4.7-rc4 next-20160624]
> [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/Marcel-Ziswiler/arm-
> tegra-initial-support-for-apalis-tk1/20160619-091204
> base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux
> for-next
> config: arm-tegra_defconfig (attached as .config)
> compiler: arm-linux-gnueabi-gcc (Debian 5.3.1-8) 5.3.1 20160205
> reproduce:
> wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tes
> ts.git/plain/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 (duplicate_label): Duplicate label 'pinmux' on /pinmux@70000
> 868 and /pinmux@0,70000868
> >
> > >
> > > ERROR: Input tree has errors, aborting (use -f to force output)
> ---
> 0-DAY kernel test infrastructure Open Source
> Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel
> Corporation
Yes, as stated under 'changes in v2' this depends on below patch as
well:
- remove commas from unit addresses as suggested by Rob (this requires
the separate patch to clean up tegra124.dtsi as well as all the other
boards basing on it to be applied first)
https://patchwork.kernel.org/patch/9185977/
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2016-06-26 20:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-19 1:08 [PATCH v3 1/3] arm: tegra: initial support for apalis tk1 Marcel Ziswiler
2016-06-19 1:08 ` [PATCH v3 2/3] arm: tegra: add colibri t30 device tree binding documentation Marcel Ziswiler
2016-06-19 1:08 ` [PATCH v3 3/3] arm: tegra: add apalis tk1 " Marcel Ziswiler
[not found] ` <1466298484-1098-1-git-send-email-marcel.ziswiler-2KBjVHiyJgBBDgjK7y7TUQ@public.gmane.org>
2016-06-26 3:52 ` [PATCH v3 1/3] arm: tegra: initial support for apalis tk1 kbuild test robot
2016-06-26 20:09 ` Marcel Ziswiler [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=1466971755.3308.3.camel@toradex.com \
--to=marcel.ziswiler@toradex.com \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lkp@intel.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).