From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Zachary Amsden <zach@vmware.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
Virtualization Mailing List <virtualization@lists.osdl.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: Paravirt-ops VMI / Xen / lrustyvisor merge status
Date: Thu, 08 Feb 2007 22:10:27 -0800 [thread overview]
Message-ID: <45CC1053.9080501@goop.org> (raw)
In-Reply-To: <45CC0672.7090201@vmware.com>
Zachary Amsden wrote:
> Chris / Jeremy - perhaps I missed it, but I haven't seen updated Xen
> paravirt-ops patches go out yet - is 2.6.21 still the merge target?
Yes. I spent today updating to address the review comments, and I think
Chris is in the process of rebasing to .20 for a repost soon (tomorrow?).
> I don't want to be pushy, but I do want our code to get merged, and
> time's a ticking.
Me too. I'm eager to be getting on to something else (which probably
means SMP at this point).
J
next prev parent reply other threads:[~2007-02-09 6:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 5:28 Paravirt-ops VMI / Xen / lrustyvisor merge status Zachary Amsden
2007-02-09 5:54 ` Rusty Russell
2007-02-09 6:12 ` Zachary Amsden
2007-02-09 6:24 ` Jeremy Fitzhardinge
2007-02-09 6:58 ` Zachary Amsden
2007-02-09 6:44 ` Rusty Russell
2007-02-09 6:57 ` Jeremy Fitzhardinge
2007-02-09 6:59 ` Zachary Amsden
2007-02-09 7:06 ` Jeremy Fitzhardinge
2007-02-09 7:20 ` Rusty Russell
2007-02-09 7:35 ` Andi Kleen
2007-02-09 8:46 ` Rusty Russell
2007-02-09 6:10 ` Jeremy Fitzhardinge [this message]
2007-02-09 7:21 ` Andi Kleen
2007-02-09 7:35 ` Zachary Amsden
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=45CC1053.9080501@goop.org \
--to=jeremy@goop.org \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=virtualization@lists.osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).