public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>,
	Nicolas Ferre <nicolas.ferre@atmel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Alan Tull <atull@opensource.altera.com>,
	Dinh Nguyen <dinguyen@opensource.altera.com>,
	Kevin Hilman <khilman@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-20150629 build: 1 failures 74 warnings (next-20150629)
Date: Mon, 29 Jun 2015 18:02:45 +0100	[thread overview]
Message-ID: <20150629170245.GI11162@sirena.org.uk> (raw)
In-Reply-To: <E1Z9WQC-000356-Bd@optimist>

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

On Mon, Jun 29, 2015 at 11:36:17AM +0100, Build bot for Mark Brown wrote:

> 	arm-allmodconfig
> ../arch/arm/mach-socfpga/pm.c:59:2: error: implicit declaration of function 'dev_get_gen_pool' [-Werror=implicit-function-declaration]

For a short while now -next has been failing to build an ARM
allmodconfig due to a collision between "genalloc: rename
dev_get_gen_pool() to gen_pool_get()" in the akpm tree and "ARM:
socfpga: support suspend to ram" which as been added via the arm-soc
tree and introduces a new use.

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

  reply	other threads:[~2015-06-29 17:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-29 10:36 next-20150629 build: 1 failures 74 warnings (next-20150629) Build bot for Mark Brown
2015-06-29 17:02 ` Mark Brown [this message]
2015-06-29 17:06 ` Mark Brown
2015-06-30  6:11   ` Jan Kara
2015-06-29 17:15 ` Mark Brown

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=20150629170245.GI11162@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=atull@opensource.altera.com \
    --cc=dinguyen@opensource.altera.com \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=khilman@linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-next@vger.kernel.org \
    --cc=nicolas.ferre@atmel.com \
    --cc=vladimir_zapolskiy@mentor.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