public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: next-20160503 build: 1 failures 12 warnings (next-20160503)
Date: Mon, 09 May 2016 13:17:19 +0200	[thread overview]
Message-ID: <4516208.OQ3mKD6WuY@wuerfel> (raw)
In-Reply-To: <20160509205315.631e0c68@canb.auug.org.au>

On Monday 09 May 2016 20:53:15 Stephen Rothwell wrote:
> Hi Arnd and all,
> 
> On Tue, 03 May 2016 17:02:39 +0200 Arnd Bergmann <arnd@arndb.de> wrote:
> >
> > On Tuesday 03 May 2016 15:17:23 Mark Brown wrote:
> > > On Tue, May 03, 2016 at 01:53:18PM +0100, Build bot for Mark Brown wrote:
> > > 
> > > Today's -next fails to build an ARM allmodconfig due to:
> > >   
> > > >       arm-allmodconfig
> > > > ../drivers/pinctrl/bcm/pinctrl-ns2-mux.c:540:17: error: 'pinctrl_utils_dt_free_map' undeclared here (not in a function)  
> > > 
> > > caused by b5aa1006e4a93 (pinctrl: ns2: add pinmux driver support for
> > > Broadcom NS2 SoC) - presumably just a missing dependency.
> > >   
> > 
> > No, the function got renamed in another patch. I already prepared a fix
> > yesterday, but haven't gotten around to submit the patches for the last
> > two days, I'll try to send it out today, but it might end up being
> > tomorrow, or Linus could fix this one himself first.
> 
> Can we, please, get this fixed ... less than a week to the merge window
> opening ...

Linus Walleij just picked up the patch I sent last week into the pinctrl tree,
so it should be fine in tomorrow's linux-next.

	Arnd

  reply	other threads:[~2016-05-09 11:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1axZpG-000664-AK@optimist>
2016-05-03 14:17 ` next-20160503 build: 1 failures 12 warnings (next-20160503) Mark Brown
2016-05-03 15:02   ` Arnd Bergmann
2016-05-09 10:53     ` Stephen Rothwell
2016-05-09 11:17       ` Arnd Bergmann [this message]
2016-05-09 18:29         ` Stephen Rothwell
2016-05-09 13:12       ` Linus Walleij
2016-05-09 18:36         ` Stephen Rothwell

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=4516208.OQ3mKD6WuY@wuerfel \
    --to=arnd@arndb.de \
    --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