From: Greg KH <gregkh@linuxfoundation.org>
To: "K. Y. Srinivasan" <kys@microsoft.com>, jbottomley@parallels.com
Cc: linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
virtualization@lists.osdl.org, ohering@suse.com,
hch@infradead.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/1] Staging: hv: storvsc: Move the storage driver out of the staging area
Date: Fri, 10 Feb 2012 10:02:12 -0800 [thread overview]
Message-ID: <20120210180212.GA605@kroah.com> (raw)
In-Reply-To: <1328825688-4337-1-git-send-email-kys@microsoft.com>
On Thu, Feb 09, 2012 at 02:14:48PM -0800, K. Y. Srinivasan 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.
>
> James was willing to apply this patch during the 3.3-rc phase and a decision
> was taken to defer this to 3.4 since Greg had queued up a bunch of storvsc
> patches for 3.4. Now that Greg has applied all of the pending storvsc patches,
> I am sending this patch to move this driver out of staging. Based on James'
> recommendation, this patch gets rid of the unneeded files in the staging/hv
> directory.
>
> Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
> ---
> drivers/scsi/Kconfig | 7 +++++++
> drivers/scsi/Makefile | 3 +++
> drivers/{staging/hv => scsi}/storvsc_drv.c | 0
> drivers/staging/Kconfig | 2 --
> drivers/staging/Makefile | 1 -
> drivers/staging/hv/Kconfig | 5 -----
> drivers/staging/hv/Makefile | 3 ---
> drivers/staging/hv/TODO | 5 -----
> 8 files changed, 10 insertions(+), 16 deletions(-)
> rename drivers/{staging/hv => scsi}/storvsc_drv.c (100%)
> delete mode 100644 drivers/staging/hv/Kconfig
> delete mode 100644 drivers/staging/hv/Makefile
> delete mode 100644 drivers/staging/hv/TODO
James, can I add your Acked-by: for this patch?
thanks,
greg k-h
next prev parent reply other threads:[~2012-02-10 18:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 22:14 [PATCH 1/1] Staging: hv: storvsc: Move the storage driver out of the staging area K. Y. Srinivasan
2012-02-10 18:02 ` Greg KH [this message]
2012-02-13 18:59 ` KY Srinivasan
2012-02-13 19:28 ` James Bottomley
2012-02-13 19:31 ` KY Srinivasan
-- strict thread matches above, loose matches on Subject: below --
2012-02-09 20:04 K. Y. Srinivasan
2012-02-09 20:04 ` Greg KH
2012-02-09 20:18 ` James Bottomley
2012-02-09 20:21 ` KY Srinivasan
2012-02-09 20:40 ` James Bottomley
2012-02-09 20:24 ` Greg KH
2012-02-09 20:43 ` KY Srinivasan
2012-02-09 20:45 ` James Bottomley
2012-02-09 20:51 ` KY Srinivasan
2012-02-09 22:13 ` KY Srinivasan
2012-02-10 11:12 ` KY Srinivasan
2012-01-25 18:29 K. Y. Srinivasan
2012-01-26 16:07 ` James Bottomley
2012-01-26 17:17 ` Rolf Eike Beer
2012-01-26 17:24 ` KY Srinivasan
2012-01-12 21:15 K. Y. Srinivasan
2011-12-07 16:16 K. Y. Srinivasan
2011-12-08 10:37 ` Rolf Eike Beer
2011-12-01 13:43 K. Y. Srinivasan
2011-11-08 18:13 K. Y. Srinivasan
2011-11-17 18:26 ` James Bottomley
2011-11-18 4:53 ` KY Srinivasan
2011-11-18 17:00 ` James Bottomley
2011-11-18 23:28 ` KY Srinivasan
2011-11-30 13:46 ` KY Srinivasan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120210180212.GA605@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@linuxdriverproject.org \
--cc=hch@infradead.org \
--cc=jbottomley@parallels.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=ohering@suse.com \
--cc=virtualization@lists.osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).