From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: xen-devel@lists.xensource.com, M A Young <m.a.young@durham.ac.uk>
Subject: Re: xen patches are in 2.6.37
Date: Fri, 29 Oct 2010 09:49:57 -0700 [thread overview]
Message-ID: <4CCAFB35.6030505@goop.org> (raw)
In-Reply-To: <20101029094641.GL2804@reaktio.net>
On 10/29/2010 02:46 AM, Pasi Kärkkäinen wrote:
> On Fri, Oct 29, 2010 at 08:36:54AM +0100, M A Young wrote:
>> Linus has merged branch 'stable/xen-pcifront-0.8.2' of
>> git://git./linux/kernel/git/konrad/xen
>> and branch 'for-linus' of
>> git://xenbits.xen.org/people/sstabellini/linux-pvhvm at
>> http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6-stable.git;a=commit;h=18cb657ca1bafe635f368346a1676fb04c512edf
>>
> Congratulations to everyone involved!! Great job.
>
> So what's the next step for dom0 upstreaming? backend drivers?
Yes, we need to come up with a set of backends that are upstreamable.
There's also a bunch of auxillary things like ACPI power management, CPU
hotplug, etc which need to be adapted and put through the upstreaming
wringer.
My thoughts about development from now are:
Main Xen development will migrate to the (newly created) xen/next-2.6.37
branch. At the moment this is more or less exactly upstream, with a
couple of little fixes added.
xen/next-2.6.32 (= xen/stable-2.6.32.x) will move to a more maintenance
state. They'll be maintained for as long as kernel.org maintains
2.6.32, but the bar for including patches will be higher (definitely
bugfixes, new features if they're not too intrusive, etc).
Therefore the development model will tend towards developing on current
kernels and backporting where necessary, rather than working on old
kernels and forward-porting.
J
next prev parent reply other threads:[~2010-10-29 16:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 7:36 xen patches are in 2.6.37 M A Young
2010-10-29 9:46 ` Pasi Kärkkäinen
2010-10-29 12:12 ` Stefano Stabellini
2010-10-29 14:45 ` Konrad Rzeszutek Wilk
2010-10-29 16:19 ` Bruce Edge
2010-10-29 16:49 ` Jeremy Fitzhardinge [this message]
2010-10-29 18:10 ` Josip Rodin
2010-10-30 19:29 ` Jeremy Fitzhardinge
2010-10-30 16:04 ` Thomas Goirand
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=4CCAFB35.6030505@goop.org \
--to=jeremy@goop.org \
--cc=m.a.young@durham.ac.uk \
--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.