From: John Garry <john.garry@huawei.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: <jejb@linux.vnet.ibm.com>, <linuxarm@huawei.com>,
<linux-kernel@vger.kernel.org>, <linux-scsi@vger.kernel.org>,
Xiang Chen <chenxiang66@hisilicon.com>
Subject: Re: [PATCH v3 4/4] scsi: hisi_sas: Add support for DIF feature for v3 hw
Date: Wed, 5 Dec 2018 15:12:27 +0000 [thread overview]
Message-ID: <9c08d3fa-5043-7d38-7b6c-574b7344409b@huawei.com> (raw)
In-Reply-To: <yq1k1kosorw.fsf@oracle.com>
On 05/12/2018 02:14, Martin K. Petersen wrote:
>
> John,
Hi Martin,
>
>> Are you happy for us to make DIX support in this driver "hisi_sas DIX
>> experimental" short term?
>
> That's entirely your call, it's your driver/controller. I just want the
> experimental tag to be due to reasons on *your* end.
>
Well unfortunately at the moment we cannot definitively say that it is
an issue on our end. There's a reasonable chance it is.
> If it's reasons on my end they'll need to get fixed. We shouldn't have
> drivers circumventing features because of bugs in the core block/SCSI
> code...
>
Right, of course not. I'm just a bit stuck now, since we need to
upstream the DIF support ASAP, but it is being held back by the DIX support.
You did request not to throw away DIX support, so I can send a new
patchset with DIF and DIX support separated out, and we can leave the
DIX patch in limbo until we get to the bottom of the DIX issue.
I hope it's ok.
Thanks,
John
next prev parent reply other threads:[~2018-12-05 15:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 12:09 [PATCH v3 0/3] hisi_sas: DIF support John Garry
2018-12-03 12:09 ` [PATCH v3 1/4] scsi: hisi_sas: Fix warnings detected by sparse John Garry
2018-12-03 12:09 ` [PATCH v3 2/4] scsi: hisi_sas: Relocate some code to reduce complexity John Garry
2018-12-03 12:09 ` [PATCH v3 3/4] scsi: hisi_sas: Make sg_tablesize consistent value John Garry
2018-12-03 12:09 ` [PATCH v3 4/4] scsi: hisi_sas: Add support for DIF feature for v3 hw John Garry
2018-12-04 4:12 ` Martin K. Petersen
2018-12-04 12:16 ` John Garry
2018-12-05 2:14 ` Martin K. Petersen
2018-12-05 15:12 ` John Garry [this message]
2018-12-06 4:17 ` Martin K. Petersen
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=9c08d3fa-5043-7d38-7b6c-574b7344409b@huawei.com \
--to=john.garry@huawei.com \
--cc=chenxiang66@hisilicon.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=martin.petersen@oracle.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
all inboxes | Powered by JetHome®