linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Neil Horman <nhorman@tuxdriver.com>
Subject: Re: linux-next: build warning after merge of the final tree
Date: Fri, 19 Apr 2013 11:44:35 +0200	[thread overview]
Message-ID: <20130419094434.GC17148@8bytes.org> (raw)
In-Reply-To: <20130419180724.a0fecca0869e712e48e430f2@canb.auug.org.au>

On Fri, Apr 19, 2013 at 06:07:24PM +1000, Stephen Rothwell wrote:
> After merging the final tree, today's linux-next build (i386 defconfig)
> produced this warning:
> 
> In file included from arch/x86/kernel/early-quirks.c:21:0:
> arch/x86/include/asm/irq_remapping.h:87:58: warning: 'struct irq_chip' declared inside parameter list [enabled by default]
> arch/x86/include/asm/irq_remapping.h:87:58: warning: its scope is only this definition or declaration, which is probably not what you want [enabled by default]
> arch/x86/include/asm/irq_remapping.h:93:18: warning: 'struct irq_chip' declared inside parameter list [enabled by default]
> 
> Probably caused by commit 03bbcb2e7e29 ("iommu/vt-d: add quirk for broken
> interrupt remapping on 55XX chipsets") from the iommu tree.

Thanks for the report, Stephen. I will queue a fix for that problem
asap.


	Joerg

  reply	other threads:[~2013-04-19  9:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-19  8:07 linux-next: build warning after merge of the final tree Stephen Rothwell
2013-04-19  9:44 ` Joerg Roedel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-05-29  5:29 Stephen Rothwell
2013-05-29  5:44 ` David Miller
2012-12-17  3:22 Stephen Rothwell
2012-12-17  3:34 ` Stephen Rothwell
2012-12-17 20:59   ` Andrew Morton
2012-08-02  4:04 Stephen Rothwell
2012-08-02 14:45 ` Nathan Zimmer
2012-03-26  4:11 Stephen Rothwell
2012-03-28  7:59 ` Williams, Dan J
2011-08-16  5:22 Stephen Rothwell
2011-08-16  6:04 ` Herbert Xu
2011-08-16  7:03   ` Stephen Rothwell
2011-08-16  7:08     ` Herbert Xu
2011-07-22  6:24 Stephen Rothwell
2011-07-22  6:26 ` David Miller
2010-09-29  4:02 Stephen Rothwell
2010-09-16  5:05 Stephen Rothwell
2010-09-16  6:29 ` Jens Axboe
2010-05-26  5:15 Stephen Rothwell
2010-03-01  8:14 Stephen Rothwell

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=20130419094434.GC17148@8bytes.org \
    --to=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=sfr@canb.auug.org.au \
    /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).