From: Joerg Roedel <jroedel@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: "Salva Peiró" <speirofr@gmail.com>,
"Joe Perches" <joe@perches.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
kernel-build-reports@lists.linaro.org,
linaro-kernel@lists.linaro.org, linux-next@vger.kernel.org,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: next-20150806 build: 2 failures 52 warnings (next-20150806)
Date: Thu, 6 Aug 2015 22:17:24 +0200 [thread overview]
Message-ID: <20150806201724.GC10112@suse.de> (raw)
In-Reply-To: <20150806180156.GC20873@sirena.org.uk>
On Thu, Aug 06, 2015 at 07:01:56PM +0100, Mark Brown wrote:
> 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.
Whoops. Thanks for the report, I'll fix it tomorrow.
Joerg
WARNING: multiple messages have this Message-ID (diff)
From: jroedel@suse.de (Joerg Roedel)
To: linux-arm-kernel@lists.infradead.org
Subject: next-20150806 build: 2 failures 52 warnings (next-20150806)
Date: Thu, 6 Aug 2015 22:17:24 +0200 [thread overview]
Message-ID: <20150806201724.GC10112@suse.de> (raw)
In-Reply-To: <20150806180156.GC20873@sirena.org.uk>
On Thu, Aug 06, 2015 at 07:01:56PM +0100, Mark Brown wrote:
> 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.
Whoops. Thanks for the report, I'll fix it tomorrow.
Joerg
next prev parent reply other threads:[~2015-08-06 20:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 11:00 next-20150806 build: 2 failures 52 warnings (next-20150806) Build bot for Mark Brown
2015-08-06 17:19 ` Mark Brown
2015-08-06 18:50 ` Andy Gross
2015-08-06 17:27 ` Mark Brown
2015-08-06 17:27 ` Mark Brown
2015-08-06 21:52 ` James Hogan
2015-08-06 21:52 ` James Hogan
2015-08-06 17:53 ` Mark Brown
2015-08-06 21:39 ` Stephen Rothwell
2015-08-07 1:56 ` Jiang Liu
2015-08-07 9:49 ` Mark Brown
2015-08-10 18:31 ` Bjorn Helgaas
2015-08-12 8:21 ` Jiang Liu
2015-08-18 12:47 ` Thomas Gleixner
2015-08-18 15:45 ` [Bugfix] PCI: Fix a typo in file pcie-xilinx.c caused by commit e39758e0ea76 Jiang Liu
2015-08-18 15:45 ` Jiang Liu
2015-08-18 16:09 ` [tip:irq/core] PCI: xilinx: Fix typo in function name tip-bot for Jiang Liu
2015-08-06 18:01 ` next-20150806 build: 2 failures 52 warnings (next-20150806) Mark Brown
2015-08-06 18:01 ` Mark Brown
2015-08-06 20:17 ` Joerg Roedel [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=20150806201724.GC10112@suse.de \
--to=jroedel@suse.de \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=joe@perches.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=speirofr@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.