[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1327600244.6151.5.camel@dabdike.int.hansenpartnership.com>
Date: Thu, 26 Jan 2012 11:50:44 -0600
From: James Bottomley <James.Bottomley@...senPartnership.com>
To: Greg KH <gregkh@...e.de>
Cc: "K. Y. Srinivasan" <kys@...rosoft.com>,
linux-kernel@...r.kernel.org, devel@...uxdriverproject.org,
virtualization@...ts.osdl.org, ohering@...e.com, hch@...radead.org,
linux-scsi@...r.kernel.org
Subject: Re: [PATCH 1/2] Staging: hv: Applied all the patches already in the
staging queue
On Thu, 2012-01-26 at 09:37 -0800, Greg KH wrote:
> 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@...rosoft.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.
Agreed
> 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?
Well, we were going to try to stage this driver for 3.3-rc. If everyone
agrees to push it back to 3.4, then this works for me.
James
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists