From: Christoph Hellwig <hch@infradead.org>
To: Bart Van Assche <Bart.VanAssche@sandisk.com>
Cc: "jejb@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"longli@microsoft.com" <longli@microsoft.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"sthemmin@microsoft.com" <sthemmin@microsoft.com>,
"kys@microsoft.com" <kys@microsoft.com>
Subject: Re: [PATCH] scsi: zero per-cmd driver data for each MQ I/O
Date: Wed, 17 May 2017 23:54:54 -0700 [thread overview]
Message-ID: <20170518065454.GA25180@infradead.org> (raw)
In-Reply-To: <1495062317.2679.1.camel@sandisk.com>
On Wed, May 17, 2017 at 11:05:18PM +0000, Bart Van Assche wrote:
> Thank you for the feedback. I'm working on a patch series that merges the scsi-sq
> and scsi-mq code paths for command initialization and that should fix the bug you
> encountered.
While that sounds great (I tried it a while ago but gave up due to
priorities) I think we should merge this patch as-is and backport it
to stable for now and rebase your series on top of it.
next prev parent reply other threads:[~2017-05-18 6:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 23:32 [PATCH] scsi: zero per-cmd driver data for each MQ I/O Long Li
2017-05-16 0:00 ` Bart Van Assche
2017-05-16 17:31 ` Long Li
2017-05-17 23:05 ` Bart Van Assche
2017-05-18 6:54 ` Christoph Hellwig [this message]
2017-05-18 13:29 ` KY Srinivasan
2017-05-18 15:52 ` Bart Van Assche
2017-05-18 16:47 ` Long Li
-- strict thread matches above, loose matches on Subject: below --
2017-05-10 21:07 Long Li
2017-05-15 22:48 ` Long Li
2017-05-15 23:20 ` KY Srinivasan
2017-05-18 6:55 ` Christoph Hellwig
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=20170518065454.GA25180@infradead.org \
--to=hch@infradead.org \
--cc=Bart.VanAssche@sandisk.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=martin.petersen@oracle.com \
--cc=sthemmin@microsoft.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