From: Rusty Russell <rusty@rustcorp.com.au>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andi Kleen <ak@suse.de>, Zachary Amsden <zach@vmware.com>,
Avi Kivity <avi@qumranet.com>,
Anthony Liguori <anthony@codemonkey.ws>,
Glauber de Oliveira Costa <glommer@gmail.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>
Subject: Re: [PATCH RFC 2/2] paravirt: clean up lazy mode handling
Date: Tue, 16 Oct 2007 10:04:42 +1000 [thread overview]
Message-ID: <200710161004.43338.rusty@rustcorp.com.au> (raw)
In-Reply-To: <470FDBC4.4050306@goop.org>
On Saturday 13 October 2007 06:40:36 Jeremy Fitzhardinge wrote:
> [ Changes since last post: fixed up lguest ]
This is really nice. Thanks Jeremy!
This will conflict a little with my own churn (file movement), but no great
drama if it goes in soon.
Acked-by: Rusty Russell <rusty@rustcorp.com.au>
next prev parent reply other threads:[~2007-10-16 0:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 20:40 [PATCH RFC 2/2] paravirt: clean up lazy mode handling Jeremy Fitzhardinge
2007-10-16 0:04 ` Rusty Russell [this message]
2007-10-16 1:54 ` Glauber de Oliveira Costa
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=200710161004.43338.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=ak@suse.de \
--cc=anthony@codemonkey.ws \
--cc=avi@qumranet.com \
--cc=glommer@gmail.com \
--cc=jeremy@goop.org \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zach@vmware.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.