From: Rusty Russell <rusty@rustcorp.com.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Avi Kivity <avi@qumranet.com>, Andi Kleen <ak@muc.de>,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
kvm-devel <kvm-devel@lists.sourceforge.net>,
Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [PATCH] make KVM conform to sucky rdmsr interface
Date: Fri, 23 Mar 2007 12:10:43 +1100 [thread overview]
Message-ID: <1174612243.2713.162.camel@localhost.localdomain> (raw)
In-Reply-To: <20070322143011.0cf83370.akpm@linux-foundation.org>
On Thu, 2007-03-22 at 14:30 -0700, Andrew Morton wrote:
> Which tree are you patching??
We crossed in the mail: you turfed out the paravirt.h cleanup patch it
applied to.
We have rolled the fixes one patch, and am testing...
Rusty.
prev parent reply other threads:[~2007-03-23 1:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 2:51 [PATCH] make KVM conform to sucky rdmsr interface Rusty Russell
2007-03-22 7:20 ` Avi Kivity
2007-03-22 7:49 ` Rusty Russell
2007-03-22 7:55 ` Jeremy Fitzhardinge
2007-03-22 21:30 ` Andrew Morton
2007-03-22 22:01 ` Jeremy Fitzhardinge
2007-03-23 1:10 ` Rusty Russell [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=1174612243.2713.162.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=ak@muc.de \
--cc=akpm@linux-foundation.org \
--cc=avi@qumranet.com \
--cc=jeremy@goop.org \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox