> The storage driver (storvsc_drv.c) handles all block storage devices > assigned to Linux guests hosted on Hyper-V. This driver has been in the > staging tree for a while and this patch moves it out of the staging area. > As per Greg's recommendation, this patch makes no changes to the > staging/hv > directory. Once the driver moves out of staging, we will cleanup the > staging/hv directory. > > This patch includes all the patches that I have sent against the > staging/hv > tree to address the comments I have gotten to date on this storage driver. > > Signed-off-by: K. Y. Srinivasan <kys@xxxxxxxxxxxxx> > --- > drivers/scsi/Kconfig | 7 + > drivers/scsi/Makefile | 3 + > drivers/scsi/storvsc_drv.c | 1586 > ++++++++++++++++++++++++++++++++++++++++++++ > 3 files changed, 1596 insertions(+), 0 deletions(-) > create mode 100644 drivers/scsi/storvsc_drv.c > > diff --git a/drivers/scsi/Kconfig b/drivers/scsi/Kconfig > index 06ea3bc..4910269 100644 > --- a/drivers/scsi/Kconfig > +++ b/drivers/scsi/Kconfig > @@ -662,6 +662,13 @@ config VMWARE_PVSCSI > To compile this driver as a module, choose M here: the > module will be called vmw_pvscsi. > > +config HYPERV_STORAGE > + tristate "Microsoft Hyper-V virtual storage driver" > + depends on SCSI && HYPERV > + default HYPERV > + help > + Select this option to enable the Hyper-V virtual storage driver. > + > config LIBFC > tristate "LibFC module" > select SCSI_FC_ATTRS Maybe that help text could be slightly more verbose? Like "This is only necessary if you plan to run this kernel as a guest on Microsoft Hyper-V"? And I would welcome the usual "the module will be called" text for this driver, too. See the first 2 lines of context of think hunk for a copy&paste source of this text. Eike _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
