Greg, 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. Regards, K. Y
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.
On Thu, May 19, 2011 at 03:06:25PM -0700, K. Y. Srinivasan wrote:> > Greg, > > 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.The merge window is closed now, and I'm on the road in asia for about 3 weeks, so doing this, at this point in the development cycle, is going to be hard. I'll go review the bus code again after the code is all merged with Linus, which should take a week or so depending on my schedule, and let you know what's left to do (I think there still is something wierd with the way the hv_driver is structured, but I could be wrong.) In the mean time, I'm sure the block and network driver still need a lot of work, and merging the bus code doesn't make much sense without them as a user as that is what people really want to use, so you can continue to work on them. thanks, greg k-h
> -----Original Message----- > From: Christoph Hellwig [mailto:hch at infradead.org] > Sent: Sunday, May 22, 2011 7:00 AM > To: KY Srinivasan > Cc: Christoph Hellwig; gregkh at suse.de; linux-kernel at vger.kernel.org; > devel at linuxdriverproject.org; virtualization at lists.osdl.org > Subject: Re: vmbus driver > > > 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. > > just send it to both of the with linux-kernel in Cc, and either of them > will probably put it in. >Will do. Thanks, K. Y
> -----Original Message----- > From: Christoph Hellwig [mailto:hch at infradead.org] > Sent: Sunday, May 22, 2011 7:00 AM > To: KY Srinivasan > Cc: Christoph Hellwig; gregkh at suse.de; linux-kernel at vger.kernel.org; > devel at linuxdriverproject.org; virtualization at lists.osdl.org > Subject: Re: vmbus driver > > > 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. > > just send it to both of the with linux-kernel in Cc, and either of them > will probably put it in. >John, Thomas, I am working on getting Hyper-V drivers (drivers/staging/hv/*) out of staging. I would like to request you to look at the Hyper-V timesource driver: drivers/staging/hv/hv_timesource.c. The supporting code for this driver is already part of the base kernel. Let me know if this driver is ready to exit staging. Regards, K. Y
On Mon, 23 May 2011, KY Srinivasan wrote:> I am working on getting Hyper-V drivers (drivers/staging/hv/*) out of staging. > I would like to request you to look at the Hyper-V timesource driver: > drivers/staging/hv/hv_timesource.c. The supporting code for this driver > is already part of the base kernel. Let me know if this driver is ready to exit staging.Can you please send a patch against drivers/clocksource (the staging part is uninteresting for review). Thanks, tglx
> -----Original Message----- > From: Thomas Gleixner [mailto:tglx at linutronix.de] > Sent: Monday, May 23, 2011 9:52 AM > To: KY Srinivasan > Cc: Christoph Hellwig; johnstul at us.ibm.com; gregkh at suse.de; linux- > kernel at vger.kernel.org; devel at linuxdriverproject.org; > virtualization at lists.osdl.org > Subject: RE: vmbus driver > > On Mon, 23 May 2011, KY Srinivasan wrote: > > I am working on getting Hyper-V drivers (drivers/staging/hv/*) out of staging. > > I would like to request you to look at the Hyper-V timesource driver: > > drivers/staging/hv/hv_timesource.c. The supporting code for this driver > > is already part of the base kernel. Let me know if this driver is ready to exit > staging. > > Can you please send a patch against drivers/clocksource (the staging > part is uninteresting for review).Will do. Regards, K. Y