> -----Original Message----- > From: Greg KH [mailto:greg@xxxxxxxxx] > Sent: Tuesday, August 23, 2011 11:00 PM > To: KY Srinivasan > Cc: gregkh@xxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; > devel@xxxxxxxxxxxxxxxxxxxxxx; virtualization@xxxxxxxxxxxxxx; Haiyang Zhang > Subject: Re: [PATCH 019/117] Staging: hv: vmbus: Cleanup vmbus_uevent() code > > On Wed, Aug 24, 2011 at 12:38:09AM +0000, KY Srinivasan wrote: > > > > > > > -----Original Message----- > > > From: Greg KH [mailto:greg@xxxxxxxxx] > > > Sent: Tuesday, August 23, 2011 6:50 PM > > > To: KY Srinivasan > > > Cc: gregkh@xxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; > > > devel@xxxxxxxxxxxxxxxxxxxxxx; virtualization@xxxxxxxxxxxxxx; Haiyang Zhang > > > Subject: Re: [PATCH 019/117] Staging: hv: vmbus: Cleanup vmbus_uevent() > code > > > > > > On Fri, Jul 15, 2011 at 10:46:07AM -0700, K. Y. Srinivasan wrote: > > > > Now generate appropriate uevent based on the modalias string. As part of > this, > > > > cleanup the existing uevent code. > > > > > > Note, you just change the user api here, did you have tools that relied > > > on the old format? If so, they just broke :( > > > > Prior to this, I don't think autoloading worked the way it should for these > > modules. > > It didn't? How did the mouse driver get autoloaded then, through the > pci/dmi tables? You are right, prior to this all drivers were loaded using pci/dmi signatures. Regards, K. Y _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
