From: Sheng Yang <sheng@linux.intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Avi Kivity <avi@qumranet.com>,
linux-next@vger.kernel.org, Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: linux-next: kvm tree build warnings
Date: Mon, 2 Mar 2009 16:00:52 +0800 [thread overview]
Message-ID: <200903021600.52820.sheng@linux.intel.com> (raw)
In-Reply-To: <20090302174915.91ccbe7f.sfr@canb.auug.org.au>
On Monday 02 March 2009 14:49:15 Stephen Rothwell wrote:
> Hi Avi,
Hi Stephen
Thanks for the notice! It's my fault...
I would post a patch to fix it. And Avi is offline this week, Marcelo is in
charge of maintenance now.
--
regards
Yang, Sheng
>
> Today's linux-next build (powerpc ppc44x_config) produced these warnings:
>
> In file included from arch/powerpc/kernel/asm-offsets.c:52:
> include/linux/kvm_host.h:368: warning: 'struct kvm_ioapic' declared inside
> parameter list include/linux/kvm_host.h:368: warning: its scope is only
> this definition or declaration, which is probably not what you want In file
> included from arch/powerpc/kvm/booke.c:24:
> include/linux/kvm_host.h:368: warning: 'struct kvm_ioapic' declared inside
> parameter list include/linux/kvm_host.h:368: warning: its scope is only
> this definition or declaration, which is probably not what you want In file
> included from arch/powerpc/kvm/booke_emulate.c:21:
> include/linux/kvm_host.h:368: warning: 'struct kvm_ioapic' declared inside
> parameter list include/linux/kvm_host.h:368: warning: its scope is only
> this definition or declaration, which is probably not what you want In file
> included from arch/powerpc/kvm/44x.c:21:
> include/linux/kvm_host.h:368: warning: 'struct kvm_ioapic' declared inside
> parameter list include/linux/kvm_host.h:368: warning: its scope is only
> this definition or declaration, which is probably not what you want In file
> included from arch/powerpc/kvm/44x_tlb.c:24:
> include/linux/kvm_host.h:368: warning: 'struct kvm_ioapic' declared inside
> parameter list include/linux/kvm_host.h:368: warning: its scope is only
> this definition or declaration, which is probably not what you want In file
> included from arch/powerpc/include/asm/kvm_ppc.h:31,
> from arch/powerpc/kvm/44x_emulate.c:21:
> include/linux/kvm_host.h:368: warning: 'struct kvm_ioapic' declared inside
> parameter list include/linux/kvm_host.h:368: warning: its scope is only
> this definition or declaration, which is probably not what you want In file
> included from arch/powerpc/kvm/../../../virt/kvm/coalesced_mmio.c:13:
> include/linux/kvm_host.h:368: warning: 'struct kvm_ioapic' declared inside
> parameter list include/linux/kvm_host.h:368: warning: its scope is only
> this definition or declaration, which is probably not what you want In file
> included from arch/powerpc/kvm/../../../virt/kvm/kvm_main.c:21:
> include/linux/kvm_host.h:368: warning: 'struct kvm_ioapic' declared inside
> parameter list include/linux/kvm_host.h:368: warning: its scope is only
> this definition or declaration, which is probably not what you want In file
> included from arch/powerpc/kvm/emulate.c:25:
> include/linux/kvm_host.h:368: warning: 'struct kvm_ioapic' declared inside
> parameter list include/linux/kvm_host.h:368: warning: its scope is only
> this definition or declaration, which is probably not what you want In file
> included from arch/powerpc/kvm/powerpc.c:24:
> include/linux/kvm_host.h:368: warning: 'struct kvm_ioapic' declared inside
> parameter list include/linux/kvm_host.h:368: warning: its scope is only
> this definition or declaration, which is probably not what you want
>
> Probably caused by commit 71c8a3f871fab4b54f7cace7d4626e67dfb51b2d ("KVM:
> Unify the delivery of IOAPIC and MSI interrupts").
prev parent reply other threads:[~2009-03-02 8:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 6:49 linux-next: kvm tree build warnings Stephen Rothwell
2009-03-02 8:00 ` Sheng Yang [this message]
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=200903021600.52820.sheng@linux.intel.com \
--to=sheng@linux.intel.com \
--cc=avi@qumranet.com \
--cc=linux-next@vger.kernel.org \
--cc=mtosatti@redhat.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).