Re: [Xen-devel] Re: pvops kernel branches - 2.6.36 options, stable/next/etc?

[Boris Derzhavets <bderzhavets@xxxxxxxxx>]

> No.  xen/next-2.6.36 doesn't exist any more, and it never really
> contained anything useful.  xen/next-2.6.37, however, is closely
> tracking upstream and I hope will reach functional parity with the
> 2.6.32-based branches.

Is 2.6.38 merge window right estimate for time frame to reach functional
parity with the 2.6.32-based branches ?

Boris.

--- On Mon, 11/8/10, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:

From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: [Xen-devel] Re: pvops kernel branches - 2.6.36 options, stable/next/etc?
To: "Bruce Edge" <bruce.edge@xxxxxxxxx>
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "Konrad Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx>
Date: Monday, November 8, 2010, 2:14 PM

On 11/08/2010 10:19 AM, Bruce Edge wrote:
> Is there now or will there be a 2.6.36 stable branch, or is the only
> option for this version the next-2.6.36 branch?

No.  xen/next-2.6.36 doesn't exist any more, and it never really
contained anything useful.  xen/next-2.6.37, however, is closely
tracking upstream and I hope will reach functional parity with the
2.6.32-based branches.

>
> In the past Jeremy has posted details on the state and forward goals
> for the major consolidation branches.
> I haven't seen any such details regarding the .36/.37 branches.
> Does any one know what the plans are?

I'll post something the next week or so when we work out what needs to
happen with .37 to get it up to speed.

>
> We've been hanging off of Konrad's  stable/xen-pcifront-0.8.2 branch
> with good results. I'm wondering what our options are now with the
> recent merge storm.

That has been merged into mainline Linux.

    J


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel