RE: [PATCH 15/77] Staging: hv: blkvsc: Add the appropriateMODULE_ALIAS() line

[KY Srinivasan]

> -----Original Message-----
> From: Greg KH [mailto:greg@xxxxxxxxx]
> Sent: Wednesday, July 06, 2011 11:29 AM
> To: KY Srinivasan
> Cc: gregkh@xxxxxxx; linux-kernel@xxxxxxxxxxxxxxx;
> devel@xxxxxxxxxxxxxxxxxxxxxx; virtualization@xxxxxxxxxxxxxx; Haiyang Zhang; Hank
> Janssen
> Subject: Re: [PATCH 15/77] Staging: hv: blkvsc: Add the appropriate
> MODULE_ALIAS() line
> 
> On Wed, Jul 06, 2011 at 03:17:37PM +0000, KY Srinivasan wrote:
> > It is certainly easier to deal with a small integer than with 128bit giud and there
> is
> > no added benefit dealing with guids since the number of drivers we will support
> > under vmbus will never exceed a very small number. Having said that, I will go
> ahead
> > and embed full guids as you have suggested. So, the aliases for these drivers
> will be:
> > vmbus:device guid.
> 
> Wait, no, you will never be typing "MODULE_ALIAS()" in your driver at
> all, it will be created automatically for you by the proper macro fun
> with the MODULE_DEVICE_TABLE() line.  The same variable you use in that
> macro will be used to register the driver with the vmbus core.

I was referring to the name that would be generated by the parsing code
In file2alias.c. I have an id_table field in the struct hv_driver and this will point
to the table that will setup. This table will be used in the vmbus match function
as well as to generate hotplug events.

Regards,

K. Y

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/