> -----Original Message----- > From: Christoph Hellwig [mailto:hch@xxxxxxxxxxxxx] > Sent: Friday, May 20, 2011 8:27 AM > To: KY Srinivasan > Cc: gregkh@xxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; > devel@xxxxxxxxxxxxxxxxxxxxxx; virtualization@xxxxxxxxxxxxxx > Subject: Re: vmbus driver > > On Thu, May 19, 2011 at 03:06:25PM -0700, K. Y. Srinivasan wrote: > > A few days ago you applied all the outstanding patches for the Hyper-V > > drivers. With these patches, I have addressed all of the known review > > comments for the vmbus driver (and a lot of comments/issues in other > > drivers as well). I am still hoping I can address > > whatever other issues/comments there might be with the intention to > > get the vmbus driver out of staging in the current window. What is your > > sense in terms of how feasible this is. From my side, I can assure you > > that I will address all legitimate issues in a very timely manner and this > > will not be dependent upon the location of the drivers (staging or > > outside staging). Looking forward to hearing from you. > > There's no point in merging it without a user. Make sure either > the network or storage driver is in a good enough shape to move with it, > to make sure the APIs it exports are actually sanely usable. > > On the other hand the HV clocksource looks mostly mergeable and doesn't > depend on vmbus. Send a patch to add it to drivers/clocksource to the > maintainer and it should be mergeable with very little remaining > cleanup. I see maintainers for each of the clocksource drivers and I see John Stultz and Thomas Gleixner listed as the maintainers for Timekeeping. Who should sign-off on the Hyper-V clocksource. Regards, K. Y _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
