> -----Original Message----- > From: Greg KH [mailto:greg@xxxxxxxxx] > Sent: Monday, March 07, 2011 6:00 PM > To: KY Srinivasan > Cc: gregkh@xxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; > devel@xxxxxxxxxxxxxxxxxxxxxx; virtualization@xxxxxxxxxxxxxx > Subject: Re: [PATCH 00/16] Staging: hv: Consolidate driver and device > abstractions > > On Mon, Mar 07, 2011 at 10:45:15PM +0000, KY Srinivasan wrote: > > > I'm guessing that you will have follow-on patches now to complete the > > > migration to the correct driver core use (i.e. proper driver and device > > > usage?) Or do you want me to look into doing this? > > > > My immediate goal is to get the vmbus driver to exit staging. To that > > end I am working on a patch-set to cleanup vmbus_drv.c. I should have this > > patch-set fairly soon. Once that is > > done, I think we would have addressed all the structural/architectural issues > > of the vmbus driver that is preventing us from exiting staging. > > Well, perhaps, let's not get ahead of ourselves here :) Certainly. I was being presumptuous when I said "we would have addressed all the structural/architectural issues ..". What I meant to say was that I would have addressed the problems that I know about. After I am done with the current cleanup, I will work on the remaining issues. > > > We are planning to address the issues with other drivers after we are done > > with the vmbus driver. As always, your help is greatly appreciated. > > The issue I am referring to above still has to do with the vmbus core. > > The goal is to have the vmbus work like all other busses in the kernel. > You register a hv_driver with some probe and disconnect callbacks, and > the vmbus calls into the drivers when it needs to. > > You are almost there, using the struct device pointers directly, but a > few more steps remain. > > I'll look into the details after your remaining cleanups, I don't want > to get in the way of them. Thank you. You should have my patches fairly soon. Hopefully, I would have addressed the issues you have raised. Regards, K. Y _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
