From: Greg KH <gregkh@suse.de>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: KY Srinivasan <kys@microsoft.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"virtualization@lists.osdl.org" <virtualization@lists.osdl.org>,
"ohering@suse.com" <ohering@suse.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"hch@infradead.org" <hch@infradead.org>,
Haiyang Zhang <haiyangz@microsoft.com>
Subject: Re: [PATCH 1/1] Staging: hv: storvsc: Move the storage driver out of staging
Date: Mon, 17 Oct 2011 08:54:42 -0700 [thread overview]
Message-ID: <20111017155442.GA14911@suse.de> (raw)
In-Reply-To: <1318865202.4794.21.camel@dabdike.int.hansenpartnership.com>
On Mon, Oct 17, 2011 at 10:26:42AM -0500, James Bottomley wrote:
> On Mon, 2011-10-17 at 15:15 +0000, KY Srinivasan wrote:
> > This patch is against Greg's staging tree where recently I merged all
> > of the storage
> > drivers into a single driver. This change may not have percolated up
> > yet - Greg has
> > checked this into his staging tree though.
>
> OK, that explains the difference.
>
> > As I deal with the review comments now, do you want me to get these
> > changes
> > applied first to Greg's tree before you would consider moving this
> > driver to drivers/scsi
> > directory, or could you move the driver as it is in Greg's tree under
> > staging and I could give
> > you patches against the moved driver.
>
> Either way is fine by me. The best route for this is to get the staging
> update into Linus head, then work on the actual SCSI problems. I'd like
> other SCSI people besides me to review it.
That will happen for the 3.2-rc1 release, so that might be the better
time to review this.
greg k-h
next prev parent reply other threads:[~2011-10-17 15:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-15 6:28 [PATCH 1/1] Staging: hv: storvsc: Move the storage driver out of staging K. Y. Srinivasan
2011-10-15 6:28 ` K. Y. Srinivasan
2011-10-15 21:27 ` James Bottomley
2011-10-16 3:01 ` KY Srinivasan
2011-10-16 3:01 ` KY Srinivasan
2011-10-17 13:59 ` James Bottomley
2011-10-17 14:10 ` Julian Andres Klode
2011-10-17 15:15 ` KY Srinivasan
2011-10-17 15:15 ` KY Srinivasan
2011-10-17 15:26 ` James Bottomley
2011-10-17 15:54 ` Greg KH [this message]
2011-10-17 23:00 ` KY Srinivasan
2011-10-17 23:00 ` KY Srinivasan
2011-10-28 23:10 ` KY Srinivasan
2011-10-28 23:10 ` 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=20111017155442.GA14911@suse.de \
--to=gregkh@suse.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.