public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "hch@infradead.org" <hch@infradead.org>
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>,
	"sthemmin@microsoft.com" <sthemmin@microsoft.com>,
	"kys@microsoft.com" <kys@microsoft.com>,
	"longli@microsoft.com" <longli@microsoft.com>,
	"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Subject: Re: [PATCH] scsi: zero per-cmd driver data for each MQ I/O
Date: Thu, 18 May 2017 15:52:23 +0000	[thread overview]
Message-ID: <1495122743.2511.5.camel@sandisk.com> (raw)
In-Reply-To: <20170518065454.GA25180@infradead.org>

On Wed, 2017-05-17 at 23:54 -0700, Christoph Hellwig wrote:
> 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.

Hello Christoph,

I will rebase my patch series on top of Long Li's patch. Long, please
repost your patch with a more detailed description and with the Reviewed-by
and Cc: stable tags added.

Thanks,

Bart.

  parent reply	other threads:[~2017-05-18 15:52 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
2017-05-18 13:29         ` KY Srinivasan
2017-05-18 15:52         ` Bart Van Assche [this message]
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=1495122743.2511.5.camel@sandisk.com \
    --to=bart.vanassche@sandisk.com \
    --cc=hch@infradead.org \
    --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