From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Joseph Glanville <joseph.glanville@orionvm.com.au>
Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Re: Linux 2.6.39 - what Xen components went in.
Date: Fri, 13 May 2011 12:49:27 -0400 [thread overview]
Message-ID: <20110513164927.GA18484@dumpdata.com> (raw)
In-Reply-To: <BANLkTim_hgQ2qPWr9aZ8OtTrurz4LqA=jw@mail.gmail.com>
On Sat, May 14, 2011 at 12:46:18AM +1000, Joseph Glanville wrote:
> Great work everyone. :)
Combined with this week acceptance of Xen in upstream QEMU, and I think
that the majority of folks on xen-devel are going to have a hard hangover
on Monday :-)
>
> I assume this means that drivers/block/xen-blkback.c is the last major
> milestone to be pushed upstream?
There are also some semi-major ones, but right now the xen-blkback is important
since it provides so much more performance benefit than the QEMU one.
next prev parent reply other threads:[~2011-05-13 16:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 14:36 Linux 2.6.39 - what Xen components went in Konrad Rzeszutek Wilk
2011-05-13 14:46 ` [Xen-devel] " Joseph Glanville
2011-05-13 16:49 ` Konrad Rzeszutek Wilk [this message]
2011-05-14 7:34 ` Sander Eikelenboom
2011-05-15 15:51 ` [Xen-users] " Pasi Kärkkäinen
2011-05-16 16:27 ` Jeremy Fitzhardinge
2011-05-16 16:49 ` Re: [Xen-devel] " Konrad Rzeszutek Wilk
2011-05-16 20:45 ` [Xen-users] " Sander Eikelenboom
2011-05-14 9:32 ` [Xen-devel] " Thomas Goirand
2011-05-14 15:02 ` Konrad Rzeszutek Wilk
2011-05-15 4:32 ` Thomas Goirand
2011-05-15 13:10 ` Pasi Kärkkäinen
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=20110513164927.GA18484@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=joseph.glanville@orionvm.com.au \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.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.