linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Guinot <simon.guinot@sequanux.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andrew Lunn <andrew@lunn.ch>,
	Gregory CLEMENT <gregory.clement@free-electrons.com>
Subject: Re: linux-next: Tree for Mar 11 (arm:multi_v5_defconfig build failure)
Date: Wed, 11 Mar 2015 17:21:41 +0100	[thread overview]
Message-ID: <20150311162140.GR1509@kw.sim.vm.gnt> (raw)
In-Reply-To: <20150311155548.GB22446@roeck-us.net>

[-- Attachment #1: Type: text/plain, Size: 1360 bytes --]

On Wed, Mar 11, 2015 at 08:55:48AM -0700, Guenter Roeck wrote:
> On Wed, Mar 11, 2015 at 04:35:58PM +1100, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Changes since 20150310:
> > 
> > New tree: drm-exynos
> > 
> > The sound-asoc tree still had its build failure so I used the version from
> > next-20150306.
> > 
> > The regulator tree lost its build failure.
> > 
> > The tip tree gained a conflict against the usb-gadget-fixes tree.
> > 
> > The staging tree lost its build failure.
> > 
> > Non-merge commits (relative to Linus' tree): 3446
> >  3448 files changed, 138744 insertions(+), 73083 deletions(-)
> > 
> > ----------------------------------------------------------------------------
> > 
> Building arm:multi_v5_defconfig ... failed
> --------------
> Error log:
> arch/arm/boot/dts/kirkwood-nas2big.dts:15:43: fatal error:
> 	dt-bindings/leds/leds-netxbig.h: No such file or directory
>  #include <dt-bindings/leds/leds-netxbig.h>
> 
> Caused by commit a9e58557e99 ("ARM: Kirkwood: add DT description for nas2big").
> Yes, that file doesn't exist.

Hi,

This should be fixed quickly. I sent a patch this morning:
http://www.spinics.net/lists/arm-kernel/msg404676.html

I believe that Gregory will merge or squash this patch soon in the
mvebu/for-next branch.

I apologize for the inconvenience.

Simon

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2015-03-11 16:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11  5:35 linux-next: Tree for Mar 11 Stephen Rothwell
2015-03-11 15:47 ` linux-next: Tree for Mar 11 (powerpc build failure due to vmx crypto code) Guenter Roeck
2015-03-12  1:23   ` Herbert Xu
2015-03-12  2:43     ` Guenter Roeck
2015-03-12  3:28       ` Herbert Xu
2015-03-12  3:51         ` Guenter Roeck
2015-03-12  3:53           ` Herbert Xu
2015-03-12 15:27             ` Leonidas S. Barbosa
2015-03-11 15:51 ` linux-next: Tree for Mar 11 (arm build failure, ASoC) Guenter Roeck
2015-03-12  6:53   ` Peter Ujfalusi
2015-03-11 15:55 ` linux-next: Tree for Mar 11 (arm:multi_v5_defconfig build failure) Guenter Roeck
2015-03-11 16:21   ` Simon Guinot [this message]
2015-03-11 16:26     ` Gregory CLEMENT

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=20150311162140.GR1509@kw.sim.vm.gnt \
    --to=simon.guinot@sequanux.org \
    --cc=andrew@lunn.ch \
    --cc=gregory.clement@free-electrons.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=sfr@canb.auug.org.au \
    /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).