> -----Original Message----- > From: Greg KH [mailto:greg@xxxxxxxxx] > Sent: Wednesday, April 27, 2011 8:28 PM > To: KY Srinivasan > Cc: gregkh@xxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; > devel@xxxxxxxxxxxxxxxxxxxxxx; virtualization@xxxxxxxxxxxxxx > Subject: Re: [PATCH 00/25] Staging: hv: Cleanup vmbus driver code > > On Wed, Apr 27, 2011 at 01:54:02AM +0000, KY Srinivasan wrote: > > > After that, do you want another round of review of the code, or do > > > you have more things you want to send in (like the name[64] removal?) > > > > I would prefer that we go through the review process. What is the process for > > this review? > > The same as always, just ask. > > > Is there a time window for people to respond. > > No. We don't have time limits here, this is a community, we don't have > deadlines, you know that. Perhaps I did not properly formulate my question here. The review process itself may be open-ended, and that is fine - we will fix all legitimate issues/concerns in our drivers whether they are in the staging area or not. My question was specifically with regards to the review process that may gate exiting staging. I am hoping to re-spin the remaining patches of the last patch-set and send it to you by early next week and ask for a review. I fully intend to address whatever review comments I may get in a very timely manner. Assuming at some point in time after I ask for this review there are no outstanding issues, would that be sufficient to exit staging? > > > I am hoping I will be able to address all the review comments well in > > advance of the next closing of the tree, with the hope of taking the > > vmbus driver out of staging this go around (hope springs eternal in > > the human breast ...)! > > Yes, it would be nice, and I understand your the corporate pressures you > are under to get this done, and I am doing my best to fit the patch > review and apply cycle into my very-very-limited-at-the-moment spare > time. Greg, I do appreciate your ongoing help here. Regards, K. Y _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
