From: Avi Kivity <avi@redhat.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: linux-next: Tree for Dec 13 (kvm/vmx.c)
Date: Wed, 14 Dec 2011 12:28:22 +0200 [thread overview]
Message-ID: <4EE87A46.2020409@redhat.com> (raw)
In-Reply-To: <4EE7E53F.5070605@xenotime.net>
On 12/14/2011 01:52 AM, Randy Dunlap wrote:
> On 12/12/2011 11:21 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20111212:
>
>
> arch/x86/built-in.o: In function `atomic_switch_perf_msrs':
> vmx.c:(.text+0x6b1d4): undefined reference to `perf_guest_get_msrs'
>
>
Thanks, patch posted.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2011-12-14 10:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 7:21 linux-next: Tree for Dec 13 Stephen Rothwell
2011-12-13 23:49 ` linux-next: Tree for Dec 13 (mrst/intel_scu/apb_timer) Randy Dunlap
2011-12-13 23:52 ` linux-next: Tree for Dec 13 (kvm/vmx.c) Randy Dunlap
2011-12-14 10:28 ` 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=4EE87A46.2020409@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--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).