mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "K. Y. Srinivasan" <kys@microsoft.com>,
	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: Thu, 09 Feb 2012 14:18:38 -0600	[thread overview]
Message-ID: <1328818718.2944.20.camel@dabdike.int.hansenpartnership.com> (raw)
In-Reply-To: <20120209200404.GA8816@kroah.com>

On Thu, 2012-02-09 at 12:04 -0800, Greg KH wrote:
> On Thu, Feb 09, 2012 at 12:04:11PM -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.
> > 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.
> > 
> > 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 re-sending this patch to move this driver out of staging.
> > 
> > 
> > Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
> > ---
> >  drivers/scsi/Kconfig       |    7 +
> >  drivers/scsi/Makefile      |    3 +
> >  drivers/scsi/storvsc_drv.c | 1548 ++++++++++++++++++++++++++++++++++++++++++++
> >  3 files changed, 1558 insertions(+), 0 deletions(-)
> >  create mode 100644 drivers/scsi/storvsc_drv.c
> 
> James, any objection to me applying this to the staging-next tree, and
> at the same time, deleting this version of the driver from the
> drivers/staging/hv/ directory?

Well, yes, it has the same build failure as the previous one and that
will make it non bisectable.

James



  reply	other threads:[~2012-02-09 20:18 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-09 20:04 K. Y. Srinivasan
2012-02-09 20:04 ` Greg KH
2012-02-09 20:18   ` James Bottomley [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2012-02-09 22:14 K. Y. Srinivasan
2012-02-10 18:02 ` Greg KH
2012-02-13 18:59   ` KY Srinivasan
2012-02-13 19:28   ` James Bottomley
2012-02-13 19:31     ` 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
2012-01-14 16:42 ` Christoph Hellwig
2012-01-14 20:31   ` KY Srinivasan
2012-01-16 15:29     ` Christoph Hellwig
2012-01-16 22:47       ` KY Srinivasan
2012-01-16 22:55       ` KY Srinivasan
2012-01-25 15:29       ` KY Srinivasan
2012-01-25 15:43         ` Christoph Hellwig
2012-01-25 15:51           ` Greg KH
2012-01-25 15:59             ` James Bottomley
2012-01-25 17:03               ` Greg KH
2012-01-25 17:12                 ` James Bottomley
2012-01-25 17:13                   ` KY Srinivasan
2012-01-25 19:22                   ` KY Srinivasan
2012-01-25 21:13                     ` KY Srinivasan
2012-01-26 14:11                   ` KY 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=1328818718.2944.20.camel@dabdike.int.hansenpartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@infradead.org \
    --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

all inboxes | Powered by JetHome®