On Fri, Jul 15, 2011 at 10:45:51AM -0700, K. Y. Srinivasan wrote: > In preparation for implementing vmbus aliases for auto-loading > Hyper-V drivers, define vmbus specific device ID. > > Signed-off-by: K. Y. Srinivasan <[email protected]> > Signed-off-by: Haiyang Zhang <[email protected]> > --- > include/linux/mod_devicetable.h | 7 +++++++ > 1 files changed, 7 insertions(+), 0 deletions(-) > > diff --git a/include/linux/mod_devicetable.h b/include/linux/mod_devicetable.h > index ae28e93..5a12377 100644 > --- a/include/linux/mod_devicetable.h > +++ b/include/linux/mod_devicetable.h > @@ -405,6 +405,13 @@ struct virtio_device_id { > }; > #define VIRTIO_DEV_ANY_ID 0xffffffff > > +/* > + * For Hyper-V devices we use the device guid as the id. > + */ > +struct hv_vmbus_device_id { > + __u8 guid[16]; > +};
Why do you not need a driver_data pointer here? Are you sure you aren't ever going to need it in the future? Hint, I think you will... greg k-h _______________________________________________ Virtualization mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/virtualization
