From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: 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>
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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150629/50c9c0e6/attachment.sig>
next parent reply other threads:[~2015-06-29 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Z9WQC-000356-Bd@optimist>
2015-06-29 17:02 ` Mark Brown [this message]
2015-06-29 17:06 ` next-20150629 build: 1 failures 74 warnings (next-20150629) 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=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