public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel•org>
To: Yendapally Reddy Dhananjaya Reddy <yendapally.reddy@broadcom•com>,
	Ray Jui <ray.jui@broadcom•com>,
	Linus Walleij <linus.walleij@linaro•org>
Cc: kernel-build-reports@lists•linaro.org,
	linaro-kernel@lists•linaro.org, linux-next@vger•kernel.org,
	linux-arm-kernel@lists•infradead.org
Subject: Re: next-20160503 build: 1 failures 12 warnings (next-20160503)
Date: Tue, 3 May 2016 15:17:23 +0100	[thread overview]
Message-ID: <20160503141723.GR6292@sirena.org.uk> (raw)
In-Reply-To: <E1axZpG-000664-AK@optimist>

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

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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2016-05-03 14:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-03 12:53 next-20160503 build: 1 failures 12 warnings (next-20160503) Build bot for Mark Brown
2016-05-03 14:17 ` Mark Brown [this message]
2016-05-03 15:02   ` Arnd Bergmann
2016-05-09 10:53     ` Stephen Rothwell
2016-05-09 11:17       ` Arnd Bergmann
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=20160503141723.GR6292@sirena.org.uk \
    --to=broonie@kernel$(echo .)org \
    --cc=kernel-build-reports@lists$(echo .)linaro.org \
    --cc=linaro-kernel@lists$(echo .)linaro.org \
    --cc=linus.walleij@linaro$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=ray.jui@broadcom$(echo .)com \
    --cc=yendapally.reddy@broadcom$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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