From: Greg KH <gregkh@suse.de>
To: "K. Y. Srinivasan" <kys@microsoft.com>
Cc: linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
virtualization@lists.osdl.org, ohering@suse.com,
jbottomley@parallels.com, hch@infradead.org,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/2] Staging: hv: Applied all the patches already in the staging queue
Date: Thu, 26 Jan 2012 09:37:51 -0800 [thread overview]
Message-ID: <20120126173751.GA14400@suse.de> (raw)
In-Reply-To: <1327599515-12679-1-git-send-email-kys@microsoft.com>
On Thu, Jan 26, 2012 at 09:38:34AM -0800, K. Y. Srinivasan wrote:
> This patch gets the storage driver to the same level as in the staging tree.
>
> Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
> ---
> drivers/staging/hv/storvsc_drv.c | 1301 ++++++++++++++++++-------------------
> 1 files changed, 633 insertions(+), 668 deletions(-)
What? That changelog comment makes no sense at all, as you are patching
the staging version of the driver. This isn't an acceptable patch at
all.
Yes, I have pending patches for this driver in my "to-apply" queue, but
that is for 3.4, not now.
So, how about I just apply those patches, and then apply a patch that
moves it out of staging into drivers/scsi/, and queue all of those up
for 3.4.
James, any objection to that?
thanks,
greg k-h
next prev parent reply other threads:[~2012-01-26 17:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 17:37 [PATCH 0000/0002] Staging: hv: Move the storage driver out of staging K. Y. Srinivasan
2012-01-26 17:38 ` [PATCH 1/2] Staging: hv: Applied all the patches already in the staging queue K. Y. Srinivasan
2012-01-26 17:37 ` Greg KH [this message]
2012-01-26 17:41 ` KY Srinivasan
2012-01-26 17:50 ` James Bottomley
2012-02-09 15:31 ` KY Srinivasan
2012-02-09 16:29 ` Greg KH
2012-02-09 16:42 ` KY Srinivasan
2012-01-26 17:38 ` [PATCH 2/2] Staging: hv: storvsc: Move the storage driver out of the staging area K. Y. 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=20120126173751.GA14400@suse.de \
--to=gregkh@suse.de \
--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