From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: next-20150806 build: 2 failures 52 warnings (next-20150806)
Date: Thu, 6 Aug 2015 19:01:56 +0100 [thread overview]
Message-ID: <20150806180156.GC20873@sirena.org.uk> (raw)
In-Reply-To: <E1ZNIul-0007IF-Ev@optimist>
On Thu, Aug 06, 2015 at 12:00:47PM +0100, Build bot for Mark Brown wrote:
Today's linux-next fails to build an ARM allmodconfig with:
> ../drivers/iommu/omap-iommu-debug.c:138:2: error: void value not ignored as it ought to be
caused by a combination of 1ba2f20ac (fs/seq_file: convert int
seq_vprint/seq_printf/etc... returns to void) which made seq_printf()
return void and e203db293863fa15 (iommu/omap: Fix debug_read_tlb() to
use seq_printf()) which has been in -next for a little while now.
-------------- 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/20150806/41897b91/attachment.sig>
next prev parent reply other threads:[~2015-08-06 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1ZNIul-0007IF-Ev@optimist>
2015-08-06 17:27 ` next-20150806 build: 2 failures 52 warnings (next-20150806) Mark Brown
2015-08-06 21:52 ` James Hogan
2015-08-06 18:01 ` Mark Brown [this message]
2015-08-06 20:17 ` Joerg Roedel
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=20150806180156.GC20873@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;
as well as URLs for NNTP newsgroup(s).