From: Avi Kivity <avi@redhat.com>
To: Zhiyong Wu <zwu.kernel@gmail.com>
Cc: kvm@vger.kernel.org, Herbert Xu <herbert@gondor.apana.org.au>,
llim@redhat.com, zhaoyang@cn.ibm.com
Subject: Re: Fix the warnings when compiling kvm user space on 2.6.29
Date: Tue, 07 Apr 2009 13:46:09 +0300 [thread overview]
Message-ID: <49DB2EF1.1010208@redhat.com> (raw)
In-Reply-To: <b1e768440904061846j48e18c28xd6b9775469bdc99b@mail.gmail.com>
Zhiyong Wu wrote:
> HI,
>
> When compiling the lastest the code for kvm user space on 2.6.29 i386,
>
> the following warnings has appeared:
>
> test/x86/msr.c:10: warning: \u2018report\u2019 defined but not used
> test/x86/msr.c:18: warning: \u2018wrmsr\u2019 defined but not used
> test/x86/msr.c:23: warning: \u2018rdmsr\u2019 defined but not used
>
>
Please send patches with a signoff, like kernel patches.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-04-07 10:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 1:46 Fix the warnings when compiling kvm user space on 2.6.29 Zhiyong Wu
2009-04-07 10:46 ` 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=49DB2EF1.1010208@redhat.com \
--to=avi@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=kvm@vger.kernel.org \
--cc=llim@redhat.com \
--cc=zhaoyang@cn.ibm.com \
--cc=zwu.kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox