From: Avi Kivity <avi@qumranet.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
kvm-devel@lists.sourceforge.net, linux-next@vger.kernel.org,
hpa <hpa@zytor.com>, mingo <mingo@redhat.com>
Subject: Re: [kvm-devel] [PATCH v2] x86: don't allow KVM_CLOCK on Voyager or Visual WS
Date: Thu, 27 Mar 2008 10:25:51 +0200 [thread overview]
Message-ID: <47EB5A0F.50908@qumranet.com> (raw)
In-Reply-To: <20080325160846.d02b0209.randy.dunlap@oracle.com>
Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> Prevent failed randconfig builds with KVM_CLOCK being enabled
> on Voyager or VISWS.
>
>
Applies, thanks.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2008-03-27 8:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-14 17:44 [PATCH] x86: don't allow KVM_CLOCK without HAVE_KVM Randy Dunlap
2008-03-14 17:44 ` Randy Dunlap
2008-03-16 11:13 ` Avi Kivity
2008-03-17 15:55 ` Randy Dunlap
2008-03-17 15:55 ` Randy Dunlap
2008-03-17 17:01 ` [kvm-devel] " Avi Kivity
2008-03-17 17:01 ` Avi Kivity
2008-03-25 23:08 ` [PATCH v2] x86: don't allow KVM_CLOCK on Voyager or Visual WS Randy Dunlap
2008-03-25 23:08 ` Randy Dunlap
2008-03-27 8:25 ` 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=47EB5A0F.50908@qumranet.com \
--to=avi@qumranet.com \
--cc=hpa@zytor.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=randy.dunlap@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.