RE: [PATCH 019/117] Staging: hv: vmbus: Cleanup vmbus_uevent() code

-----Original Message-----
From: Greg KH [mailto:greg@kroah.com]
Sent: Tuesday, August 23, 2011 11:00 PM
To: KY Srinivasan
Cc: gregkh@suse.de; linux-kernel@vger.kernel.org;
devel@linuxdriverproject.org; virtualization@lists.osdl.org; 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:

quoted

quoted

-----Original Message-----
From: Greg KH [mailto:greg@kroah.com]
Sent: Tuesday, August 23, 2011 6:50 PM
To: KY Srinivasan
Cc: gregkh@suse.de; linux-kernel@vger.kernel.org;
devel@linuxdriverproject.org; virtualization@lists.osdl.org; Haiyang Zhang
Subject: Re: [PATCH 019/117] Staging: hv: vmbus: Cleanup vmbus_uevent()

code

quoted

quoted

On Fri, Jul 15, 2011 at 10:46:07AM -0700, K. Y. Srinivasan wrote:

quoted

Now generate appropriate uevent based on the modalias string. As part of

this,

quoted

quoted

quoted

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