From mboxrd@z Thu Jan 1 00:00:00 1970 From: Harry Butterworth Subject: Re: Re: USB virt status Date: Sat, 05 Nov 2005 11:30:19 +0000 Message-ID: <1131190219.4715.7.camel@localhost> References: <1130690595.28174.13.camel@localhost> <200511041725.11451.mark.williamson@cl.cam.ac.uk> <1131130680.3019.87.camel@localhost.localdomain> <200511050050.58120.mark.williamson@cl.cam.ac.uk> <1131157306.4740.65.camel@localhost> <436C3029.5040902@comcast.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: Nivedita Singhvi , xen-devel@lists.xensource.com, Mark Williamson List-Id: xen-devel@lists.xenproject.org On Sat, 2005-11-05 at 10:32 +0000, Keir Fraser wrote: > All that's being done is the simplest possible bug fixing and > refactoring to get stable drivers for a 3.0.0 release asap. xenidc is > possibly a suitable alternative for future releases, after we have had > time to look at it, integrate it with all the split drivers, and fix > bug fallout. Given the size and complexity of the patch, I think it > would be very high risk to commit to doing that in the next couple of > weeks. Good. This seems entirely reasonable to me. So I'll release the USB driver against xenidc as an example and document and break down the xenidc patch (and run it through a reformatter) so it can be reviewed. If you like xenidc you can keep it, if not I can factor out the code later. Easy come, easy go :-) > > -- Keir > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > -- Harry Butterworth