All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: virtualization@lists.linux-foundation.org
Cc: Alexander Graf <agraf@suse.de>, kvm list <kvm@vger.kernel.org>,
	Nick Piggin <npiggin@suse.de>, Glauber Costa <glommer@redhat.com>,
	Avi Kivity <avi@redhat.com>,
	Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [PATCH 3/3] Split the KVM pv-ops support by feature
Date: Wed, 18 Nov 2009 12:03:39 +1030	[thread overview]
Message-ID: <200911181203.39955.rusty@rustcorp.com.au> (raw)
In-Reply-To: <1258503192-14246-4-git-send-email-agraf@suse.de>

On Wed, 18 Nov 2009 10:43:12 am Alexander Graf wrote:
> Currently selecting KVM guest support enabled multiple features at once that
> not everyone necessarily wants to have, namely:

These patches make perfect sense, but please make sure Jeremy Fitzhardinge
(CC'd) is in the loop, as he split the structs in the first place.

Thanks!
Rusty.

  parent reply	other threads:[~2009-11-18  1:33 UTC|newest]

Thread overview: 25+ 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-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 ` 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  0:13 ` Alexander Graf
2009-11-18  1:33   ` Rusty Russell
2009-11-18  1:33   ` Rusty Russell [this message]
2009-11-18  1:37     ` Alexander Graf
2009-11-18  1:37     ` 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:07       ` Avi Kivity
2009-12-03 15:07       ` Avi Kivity
2009-12-03 15:04     ` 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=200911181203.39955.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=agraf@suse.de \
    --cc=avi@redhat.com \
    --cc=glommer@redhat.com \
    --cc=jeremy@goop.org \
    --cc=kvm@vger.kernel.org \
    --cc=npiggin@suse.de \
    --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.