From: KY Srinivasan <kys@microsoft.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "JBottomley@parallels.com" <JBottomley@parallels.com>,
"gregkh@suse.de" <gregkh@suse.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"ohering@suse.com" <ohering@suse.com>
Subject: RE: [PATCH 1/1] Staging: hv: storvsc: Move the storage driver out of the staging area
Date: Mon, 16 Jan 2012 22:55:31 +0000 [thread overview]
Message-ID: <6E21E5352C11B742B20C142EB499E0481B6F060C@TK5EX14MBXC126.redmond.corp.microsoft.com> (raw)
In-Reply-To: <20120116152951.GA9720@infradead.org>
> -----Original Message-----
> From: Christoph Hellwig [mailto:hch@infradead.org]
> Sent: Monday, January 16, 2012 10:30 AM
> To: KY Srinivasan
> Cc: Christoph Hellwig; JBottomley@parallels.com; gregkh@suse.de; linux-
> kernel@vger.kernel.org; devel@linuxdriverproject.org; ohering@suse.com
> Subject: Re: [PATCH 1/1] Staging: hv: storvsc: Move the storage driver out of the
> staging area
>
> On Sat, Jan 14, 2012 at 08:31:18PM +0000, KY Srinivasan wrote:
> > Thanks Christoph. Would you be taking this driver out of staging or should I ask
> Greg. James had indicated that
> > he had turned the driver over to you for reviewing.
>
> In the end James still maintains the SCSI tree and send on all drivers.
> The only thing I can do is give a positive review.
James,
Let me know if there is something else you want me to address in this driver before it can exit staging.
Regards,
K. Y
next prev parent reply other threads:[~2012-01-16 22:55 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 21:15 [PATCH 1/1] Staging: hv: storvsc: Move the storage driver out of the staging area 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 [this message]
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
-- 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-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
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=6E21E5352C11B742B20C142EB499E0481B6F060C@TK5EX14MBXC126.redmond.corp.microsoft.com \
--to=kys@microsoft.com \
--cc=JBottomley@parallels.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@suse.de \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ohering@suse.com \
/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).