From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: kvm list <kvm@vger.kernel.org>, Nick Piggin <npiggin@suse.de>,
Glauber Costa <glommer@redhat.com>,
virtualization@lists.linux-foundation.org, rusty@rustcorp.com.au
Subject: Re: [PATCH 0/3] Split up pv-ops
Date: Thu, 03 Dec 2009 17:07:48 +0200 [thread overview]
Message-ID: <4B17D444.6060702@redhat.com> (raw)
In-Reply-To: <4B17D390.5050602@suse.de>
On 12/03/2009 05:04 PM, Alexander Graf wrote:
>> Don't think so. I suggest you copy lkml and Ingo.
>>
> Sending off the complete set again?
Yes.
> Rebased against what?
>
tip's x86/paravirt seems like a good choice (though only one patch is in
there at present).
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-12-03 15:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 0:13 [PATCH 0/3] Split up pv-ops Alexander Graf
2009-11-18 0:13 ` [PATCH 1/3] Split paravirt ops by functionality Alexander Graf
2009-11-18 0:13 ` Alexander Graf
2009-11-19 14:59 ` Jeremy Fitzhardinge
2009-11-19 14:59 ` Jeremy Fitzhardinge
2009-11-19 15:21 ` Alexander Graf
2009-11-19 15:21 ` Alexander Graf
2009-11-18 0:13 ` [PATCH 2/3] Only export selected pv-ops feature structs Alexander Graf
2009-11-18 0:13 ` Alexander Graf
2009-11-18 0:13 ` [PATCH 3/3] Split the KVM pv-ops support by feature Alexander Graf
2009-11-18 1:33 ` Rusty Russell
2009-11-18 1:33 ` Rusty Russell
2009-11-18 1:37 ` Alexander Graf
2009-11-18 1:37 ` Alexander Graf
2009-11-18 0:13 ` Alexander Graf
2009-11-19 7:42 ` [PATCH 0/3] Split up pv-ops Avi Kivity
2009-11-19 7:42 ` Avi Kivity
2009-12-03 14:52 ` Alexander Graf
2009-12-03 14:52 ` Alexander Graf
2009-12-03 15:00 ` Avi Kivity
2009-12-03 15:00 ` Avi Kivity
2009-12-03 15:04 ` Alexander Graf
2009-12-03 15:04 ` Alexander Graf
2009-12-03 15:07 ` Avi Kivity [this message]
2009-12-03 15:07 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2009-11-18 0:13 Alexander Graf
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=4B17D444.6060702@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=glommer@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.org \
/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.