On Fri, Sep 02, 2011 at 03:17:19PM +0000, KY Srinivasan wrote: > > > > -----Original Message----- > > From: Greg KH [mailto:greg@xxxxxxxxx] > > Sent: Thursday, September 01, 2011 4:31 PM > > To: Peter Foley > > Cc: KY Srinivasan; gregkh@xxxxxxx; Linux Kernel Mailing List; > > devel@xxxxxxxxxxxxxxxxxxxxxx; virtualization@xxxxxxxxxxxxxx > > Subject: Re: Hyper-V TODO file > > > > On Wed, Aug 31, 2011 at 07:11:39PM -0400, Peter Foley wrote: > > > On Wed, 31 Aug 2011, K. Y. Srinivasan wrote: > > > > Greg, as I have been pestering you for some time now, we are very > > interested in > > > > exiting staging and we are willing to dedicate the necessary development > > > > resources to address whatever issues that may still be pending. So, your help > > > > in identifying what needs to be done will be greatly appreciated. To that end, > > > > I think it will be useful to update the TODO file to reflect the current state of > > > > the drivers. Let us know how we should proceed here. > > > > > > An issue I've come across in the hyper-v drivers is the forced modular > > > build. You might want to see if the "depends on m" is still needed. > > > > Ah, good point, KY, can you try this out and see if that can be changed? > > If not, something is wrong and that needs to get fixed. > > Just verified that we can build into the kernel (not as modules) all hyper-V > drivers except hv_storvsc. hv_storvsc depends upon functionality that in my build > is being built as modules (SCSI etc.) and this is the reason why I could not build > hv_storvsc as part of the kernel. So 'make allyesconfig' with the module dependancy turned off doesn't break the build? If so, great. > Greg, do you want me to submit a patch to Kconfig, getting rid of the module > dependency (for hyperv-v drivers). Yes please. thanks, greg k-h _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
