Re: [PATCH] xen frontend driver module autoloading

[Gerd Hoffmann <kraxel@redhat.com>]

Jeremy Fitzhardinge wrote:
> Gerd Hoffmann wrote:
>> This patch (against 3.1-final) implements module autoloading for the xen
>> frontend drivers by adding a uevent function for the frontend xenbus and
>> some module aliases to the individual drivers.
>>   
> 
> Now that Xen is upstream,

Wow, finally, congratulations.

> could you generate the corresponding patches
> against mainline?

Ok, somewhat broader question then:  What is the plan now?  Does the
request to send patches against mainline mean that active development
happens only in mainline and the parvirt_ops patch queue?  What happens
with the sparse tree in 3.1?   What happens with the separate
2.6.18-based tree for unstable?  Are they left as-is?  Do they get
backports from mainline?  How are bits handled which are not in the
paravirt_ops queue yet (dom0, x86_64, pvfb, ...)?

cheers,
  Gerd