On Thu, Jun 16, 2011 at 01:16:48PM -0700, K. Y. Srinivasan wrote: > Add the appropriate MODULE_ALIAS() line to support auto-loading. > > Signed-off-by: K. Y. Srinivasan <[email protected]> > Signed-off-by: Haiyang Zhang <[email protected]> > Signed-off-by: Hank Janssen <[email protected]> > --- > drivers/staging/hv/blkvsc_drv.c | 1 + > 1 files changed, 1 insertions(+), 0 deletions(-) > > diff --git a/drivers/staging/hv/blkvsc_drv.c b/drivers/staging/hv/blkvsc_drv.c > index 5842db8..9496abe 100644 > --- a/drivers/staging/hv/blkvsc_drv.c > +++ b/drivers/staging/hv/blkvsc_drv.c > @@ -1027,5 +1027,6 @@ static void __exit blkvsc_exit(void) > MODULE_LICENSE("GPL"); > MODULE_VERSION(HV_DRV_VERSION); > MODULE_DESCRIPTION("Microsoft Hyper-V virtual block driver"); > +MODULE_ALIAS("vmbus:hv_block");
No, these should be automagically generated with the MODULE_DEVICE_ID() macro that you use in the module with the GUID there, instead of this. Don't look at platform drivers as any semblance of how you should ever do anything (I'm guessing you just copied their way of doing things here). You have a real bus here (or at least a half-way version of a bus) that can autodetect devices and tell userspace that you now have them. Use that, don't try to model the code after the old, broken, and hopefully-someday-in-my-dreams-will-go-away platform code. greg k-h _______________________________________________ devel mailing list [email protected] http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
