public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel•org>
To: "Salva Peiró" <speirofr@gmail•com>,
	"Joerg Roedel" <jroedel@suse•de>, "Joe Perches" <joe@perches•com>,
	"Andrew Morton" <akpm@linux-foundation•org>
Cc: 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 19:01:56 +0100	[thread overview]
Message-ID: <20150806180156.GC20873@sirena.org.uk> (raw)
In-Reply-To: <E1ZNIul-0007IF-Ev@optimist>

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

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.

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

  parent reply	other threads:[~2015-08-06 18:02 UTC|newest]

Thread overview: 14+ 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 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-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$(echo .)org \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=joe@perches$(echo .)com \
    --cc=jroedel@suse$(echo .)de \
    --cc=kernel-build-reports@lists$(echo .)linaro.org \
    --cc=linaro-kernel@lists$(echo .)linaro.org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linux-omap@vger$(echo .)kernel.org \
    --cc=speirofr@gmail$(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