linux-kernel - Re: [PATCH 1/1][RESEND] Staging: hv: storvsc: Move the storage driver out of the staging area

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CABE8wwsat+JGLiKpu_70bxZQAYegdrcsow=9XXBabwgWUgBT4Q@mail.gmail.com>
Date:	Tue, 20 Dec 2011 17:32:35 -0800
From:	"Williams, Dan J" <dan.j.williams@...el.com>
To:	KY Srinivasan <kys@...rosoft.com>
Cc:	"gregkh@...e.de" <gregkh@...e.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
	"ohering@...e.com" <ohering@...e.com>,
	"James.Bottomley@...senpartnership.com" 
	<James.Bottomley@...senpartnership.com>,
	"hch@...radead.org" <hch@...radead.org>,
	"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>
Subject: Re: [PATCH 1/1][RESEND] Staging: hv: storvsc: Move the storage driver
 out of the staging area

On Tue, Dec 20, 2011 at 4:42 PM, KY Srinivasan <kys@...rosoft.com> wrote:
>
>
>> -----Original Message-----
>> From: dan.j.williams@...il.com [mailto:dan.j.williams@...il.com] On Behalf Of
>> Dan Williams
>> Sent: Tuesday, December 20, 2011 6:06 PM
>> To: KY Srinivasan
>> Cc: gregkh@...e.de; linux-kernel@...r.kernel.org;
>> devel@...uxdriverproject.org; virtualization@...ts.osdl.org; ohering@...e.com;
>> James.Bottomley@...senpartnership.com; hch@...radead.org; linux-
>> scsi@...r.kernel.org
>> Subject: Re: [PATCH 1/1][RESEND] Staging: hv: storvsc: Move the storage driver
>> out of the staging area
>>
>> On Tue, Dec 20, 2011 at 10:51 AM, K. Y. Srinivasan <kys@...rosoft.com> wrote:
>> > 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.
>> > Greg has already applied all these patches to the staging tree.
>> >
>> > Signed-off-by: K. Y. Srinivasan <kys@...rosoft.com>
>> > ---
>> >  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
>>
>> Shouldn't this diffstat be something like the following?
>>
>>  drivers/scsi/Kconfig                       |    7 +
>>  drivers/scsi/Makefile                      |    3 +
>>  drivers/{staging/hv => scsi}/storvsc_drv.c |  310 +++++++++++++++++++---------
>>  3 files changed, 218 insertions(+), 102 deletions(-)
>>  rename drivers/{staging/hv => scsi}/storvsc_drv.c (87%)
>
> As per Greg's suggestion, this patch does not remove the driver from
> the staging tree. Once the driver lands in the correct directory, we will
> remove the driver from the staging directory.

Ah, ok, so the patch can be accepted in parallel with the staging update.

I still think it wouldn't hurt to show what:

git diff --stat --summary -M

...is after the removal of the version in drivers/staging/hv/ to
quickly show that git agrees that the versions are indeed identical,
but no big deal.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/