From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Jan Beulich <JBeulich@novell.com>
Subject: Re: full featured, fully bug-fix pv-ops branch?
Date: Mon, 9 May 2011 17:06:53 -0400 [thread overview]
Message-ID: <20110509210653.GB29498@dumpdata.com> (raw)
In-Reply-To: <20110509130740.GC32595@reaktio.net>
On Mon, May 09, 2011 at 04:07:40PM +0300, Pasi Kärkkäinen wrote:
> On Mon, May 09, 2011 at 01:16:11PM +0100, Jan Beulich wrote:
> > Jeremy, Konrad,
> >
> > stumbling over this once in a while (this time looking for where Dominic's
> > "blktap: Fix reference to freed struct request" patch ended up, without
> > any success so far) I wonder what pv-ops branch(es) is (are) supposed
> > to be the one(s) (e.g.) distros ought to use - that is, fully featured (at
> > least as far as non-experimental features go) *and* fully bug-fixed.
We should talk then - I did not want to commit to a specific branch
b/c I wasn't sure which one the majority of the distors would want
to settle one.
There is a pretty good bug-fixed (thanks to Virtual Computer) and mostly
featured (blkback, netback, blktap2) branch that I was thinking to setup
and start upstreaming the pieces.
> >
> > The branches XenParavirtOps on the wiki points to don't seem to be the
> > ones (some of them seem not to have a blktap implementation at all),
> > and gathering bits from various people's private trees can't be the
> > ultimate solution...
> >
>
> Afaik Jeremy's xen.git xen/stable-2.6.32.x is supposed to be the
> long-term stable branch, following upstream kernel.org long-term branch.
<nods>
>
> -- Pasi
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2011-05-09 21:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 12:16 full featured, fully bug-fix pv-ops branch? Jan Beulich
2011-05-09 13:07 ` Pasi Kärkkäinen
2011-05-09 21:06 ` Konrad Rzeszutek Wilk [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=20110509210653.GB29498@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@novell.com \
--cc=jeremy@goop.org \
--cc=pasik@iki.fi \
--cc=xen-devel@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.