From: Zachary Amsden <zach@vmware.com>
To: Andi Kleen <ak@suse.de>,
Virtualization Mailing List <virtualization@lists.osdl.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Chris Wright <chrisw@sous-sol.org>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Andrew Morton <akpm@osdl.org>
Subject: Paravirt-ops VMI / Xen / lrustyvisor merge status
Date: Thu, 08 Feb 2007 21:28:18 -0800 [thread overview]
Message-ID: <45CC0672.7090201@vmware.com> (raw)
So, as 2.6.21-rc1 is approaching, what is the upstream merge status for
the paravirt-ops backends? I believe VMI is in Andi's tree, plus or
minus some bugfixes that are still being whittled in, but Andi, do you
think the VMI code is in good shape for merging?
It would be nice for everyone to clarify their upstream plans - is the
goal still to get Xen and lguest merged for the next kernel release?
Rusty, you mentioned you had a patchset to push, when do you expect to
have it ready?
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?
I don't want to be pushy, but I do want our code to get merged, and
time's a ticking. I think we're all in good shape, but the sooner the
code all gets merged the sooner we can tackle the remaining cleanup /
polishing tasks. One of which is separating the paravirt-ops into GPL
and non-GPL exports, which we need consensus on where the line is, but
can't really achieve it until everyone is happy with the finalized set
of paravirt-ops. Any patch that tries to do this now would just cause
rejects later and slow all of our merges.
Zach
next reply other threads:[~2007-02-09 5:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 5:28 Zachary Amsden [this message]
2007-02-09 5:54 ` Paravirt-ops VMI / Xen / lrustyvisor merge status 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
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=45CC0672.7090201@vmware.com \
--to=zach@vmware.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=jeremy@goop.org \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.osdl.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;
as well as URLs for NNTP newsgroup(s).