From: Avi Kivity <avi@redhat.com>
To: Xiao Guangrong <xiaoguangrong.eric@gmail.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>, KVM <kvm@vger.kernel.org>
Subject: Re: [PATCH] KVM: IA64: fix struct redefinition
Date: Sun, 27 Nov 2011 14:22:28 +0200 [thread overview]
Message-ID: <4ED22B84.1070604@redhat.com> (raw)
In-Reply-To: <4ECE17C7.2080801@gmail.com>
On 11/24/2011 12:09 PM, Xiao Guangrong wrote:
> From: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
>
> There is the same struct definition in ia64 and kvm common code:
> arch/ia64/kvm//kvm-ia64.c: At top level:
> arch/ia64/kvm//kvm-ia64.c:777:8: error: redefinition of ‘struct kvm_io_range’
> include/linux/kvm_host.h:62:8: note: originally defined here
>
> So, rename kvm_io_range to kvm_ia64_io_range in ia64 code
>
Thanks, applied.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2011-11-27 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 10:09 [PATCH] KVM: IA64: fix struct redefinition Xiao Guangrong
2011-11-27 12:22 ` Avi Kivity [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=4ED22B84.1070604@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=xiaoguangrong.eric@gmail.com \
--cc=xiaoguangrong@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox