From: Avi Kivity <avi@redhat.com>
To: Zachary Amsden <zamsden@redhat.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Glauber Costa <glommer@redhat.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
kvm@vger.kernel.org, linux-next@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for November 22 (kvm)
Date: Thu, 16 Dec 2010 11:37:00 +0200 [thread overview]
Message-ID: <4D09DDBC.4090507@redhat.com> (raw)
In-Reply-To: <4D049488.5020105@redhat.com>
On 12/12/2010 11:23 AM, Avi Kivity wrote:
> On 12/10/2010 07:18 PM, Randy Dunlap wrote:
>> > Looks like this is the appropriate fix:
>> >
>> > #ifdef CONFIG_SMP
>> > static void __init kvm_smp_prepare_boot_cpu(void)
>> > {
>> > #ifdef CONFIG_KVM_CLOCK
>> > WARN_ON(kvm_register_clock("primary cpu clock"));
>> > #endif
>> > kvm_guest_cpu_init();
>> > native_smp_prepare_boot_cpu();
>> > }
>>
>>
>> Can we get this fix merged, please?
>>
>> Build error is still happening in linux-next 20101210.
>>
>
> Zach, a proper patch please.
>
Should be fixed for the next spin.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-12-16 9:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 2:49 linux-next: Tree for November 22 Stephen Rothwell
2010-11-22 12:47 ` Zimny Lech
[not found] ` <20101122134911.b7e106f9.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2010-11-22 15:37 ` Zimny Lech
2010-11-22 19:46 ` Greg KH
[not found] ` <20101122194643.GB21985-l3A5Bk7waGM@public.gmane.org>
2010-11-22 20:08 ` Arend Van Spriel
2010-11-22 21:31 ` Greg KH
2010-11-22 19:55 ` Zimny Lech
2010-11-22 21:26 ` linux-next: Tree for November 22 (kvm) Randy Dunlap
2010-11-29 16:33 ` Randy Dunlap
2010-11-29 16:35 ` Avi Kivity
2010-11-29 17:47 ` Zachary Amsden
2010-11-29 17:52 ` Randy Dunlap
2010-11-29 18:08 ` Zachary Amsden
2010-11-29 19:05 ` Randy Dunlap
2010-11-30 12:17 ` Glauber Costa
2010-11-30 18:09 ` Zachary Amsden
2010-12-10 17:18 ` Randy Dunlap
2010-12-12 9:23 ` Avi Kivity
2010-12-16 9:37 ` 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=4D09DDBC.4090507@redhat.com \
--to=avi@redhat.com \
--cc=glommer@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
--cc=zamsden@redhat.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;
as well as URLs for NNTP newsgroup(s).