public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Ian Abbott <abbotti@mev.co.uk>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-scsi@vger.kernel.org, devel@linuxdriverproject.org,
	Andy Whitcroft <apw@canonical.com>,
	"K. Y. Srinivasan" <kys@microsoft.com>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	Tim Gardner <tim.gardner@canonical.com>
Subject: Re: [PATCH 1/2] scsi: hyper-v storvsc switch up to SPC-3
Date: Fri, 16 May 2014 19:18:20 +0100	[thread overview]
Message-ID: <5376566C.5080805@mev.co.uk> (raw)
In-Reply-To: <1400263135.2221.58.camel@dabdike.int.hansenpartnership.com>

On 2014-05-16 18:58, James Bottomley wrote:
> On Fri, 2014-05-16 at 18:39 +0100, Ian Abbott wrote:
>> On 2014-05-16 18:14, James Bottomley wrote:
>>> On Fri, 2014-05-16 at 16:39 +0100, Ian Abbott wrote:
>>>> From: Andy Whitcroft <apw@canonical.com>
>>>>
>>>> Suggested-by: James Bottomley <James.Bottomley@HansenPartnership.com>
>>>
>>> That is my patch, isn't it, just with a slightly modified comment:
>>>
>>> http://marc.info/?l=linux-scsi&m=137908428211951
>>
>> I believe so, yes.  Looking at Ubuntu's kernel repository, Andy reverted
>> his original 4 patches and applied your patch instead.  I'm not sure
>> about the other patch (PATCH 2/2) that disables the MAINTENANCE_IN
>> command.  Perhaps that was needed as a consequence of claiming to be
>> SCSI level SPC-3?
>
> Yes, see other email.
>
>>> Andy promised to go off and test it and that's where the thread ended. I
>>> take it the results of the testing was positive?  I was expecting him to
>>> report back on that so KY could ack the patch.
>>>
>>> James
>>
>> The patch seems to be in Ubuntu Saucy's 3.11 kernel version 3.11.0-12.18
>> onwards - see
>> http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-saucy.git;a=log;h=refs/tags/Ubuntu-3.11.0-12.18
>> for the logs.
>>
>> Would you like me to resubmit the patch with you as the author?  There
>> isn't a "Signed-off-by:" line for you on this patch at the moment.  Is
>> it okay for me to add one?
>
> I'm not really comfortable with the way these patches are being
> submitted.  I really need Andy to justify what's been done and why, then
> find an upstream acceptable format then for the Microsoft Hyper-V guys
> to ack them.  We need more information than you can infer simply from
> the patches being in Ubuntu.  If Andy's off somewhere, we can wait
> because this is just simply feature enablement; the bug doesn't show
> unless you enable trim on hv storvsc.

TBH, I'm out of my depth on this, but hopefully I've kicked up the dust 
a bit, since the patches (good or bad) have been languishing in Ubuntu's 
repositories since October!

-- 
-=( Ian Abbott @ MEV Ltd.    E-mail: <abbotti@mev.co.uk>        )=-
-=( Tel: +44 (0)161 477 1898   FAX: +44 (0)161 718 3587         )=-

  reply	other threads:[~2014-05-16 18:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-16 15:39 [PATCH 0/2] scsi: hyper-v storvsc changes by Ubuntu Ian Abbott
2014-05-16 15:39 ` [PATCH 1/2] scsi: hyper-v storvsc switch up to SPC-3 Ian Abbott
2014-05-16 17:11   ` Dan Carpenter
2014-05-16 17:14   ` James Bottomley
2014-05-16 17:39     ` Ian Abbott
2014-05-16 17:58       ` James Bottomley
2014-05-16 18:18         ` Ian Abbott [this message]
2014-05-16 18:25           ` James Bottomley
2014-05-16 19:28             ` KY Srinivasan
2014-05-16 19:50               ` KY Srinivasan
2014-05-16 15:39 ` [PATCH 2/2] scsi: hyper-v storvsc -- host takes MAINTENANCE_IN commands badly -- elide them Ian Abbott
2014-05-16 17:42   ` James Bottomley
2014-05-21 14:24 ` [PATCH 0/2] scsi: hyper-v storvsc changes by Ubuntu Andy Whitcroft
2014-05-22 10:49   ` KY Srinivasan
2014-05-22 14:38     ` James Bottomley
2014-05-22 22:41       ` 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=5376566C.5080805@mev.co.uk \
    --to=abbotti@mev.co.uk \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=apw@canonical.com \
    --cc=devel@linuxdriverproject.org \
    --cc=haiyangz@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=tim.gardner@canonical.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