From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bart Van Assche <Bart.VanAssche@wdc.com>
Cc: "martin.petersen\@oracle.com" <martin.petersen@oracle.com>,
"jthumshirn\@suse.de" <jthumshirn@suse.de>,
Damien Le Moal <Damien.LeMoal@wdc.com>,
"hch\@lst.de" <hch@lst.de>,
"stable\@vger.kernel.org" <stable@vger.kernel.org>,
"linux-scsi\@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"brking\@linux.vnet.ibm.com" <brking@linux.vnet.ibm.com>,
"abdhalee\@linux.vnet.ibm.com" <abdhalee@linux.vnet.ibm.com>,
"hare\@suse.com" <hare@suse.com>,
"jejb\@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>,
"mpe\@ellerman.id.au" <mpe@ellerman.id.au>
Subject: Re: [PATCH] Revert "scsi-mq: Always unprepare before requeuing a request"
Date: Thu, 17 Aug 2017 12:45:51 -0400 [thread overview]
Message-ID: <yq14lt6m9c0.fsf@oracle.com> (raw)
In-Reply-To: <1502983764.2615.3.camel@wdc.com> (Bart Van Assche's message of "Thu, 17 Aug 2017 15:29:26 +0000")
Bart,
> I think this means that the ipr fix went upstream before it ended up in
> linux-next.
OK.
Brian: Please make sure you test with your ipr change in place as well
as Bart's patch. And then report back.
Thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2017-08-17 16:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 17:43 [PATCH] Revert "scsi-mq: Always unprepare before requeuing a request" Bart Van Assche
2017-08-17 0:11 ` Martin K. Petersen
2017-08-17 0:41 ` Damien Le Moal
2017-08-17 0:45 ` Damien Le Moal
2017-08-17 0:52 ` Martin K. Petersen
2017-08-17 1:29 ` Bart Van Assche
2017-08-17 2:00 ` Martin K. Petersen
2017-08-17 2:41 ` Bart Van Assche
2017-08-17 2:51 ` Martin K. Petersen
2017-08-17 15:29 ` Bart Van Assche
2017-08-17 16:45 ` Martin K. Petersen [this message]
2017-08-17 17:40 ` Brian King
2017-08-17 17:48 ` Martin K. Petersen
2017-08-18 12:06 ` Michael Ellerman
2017-08-17 0:46 ` 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=yq14lt6m9c0.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=Bart.VanAssche@wdc.com \
--cc=Damien.LeMoal@wdc.com \
--cc=abdhalee@linux.vnet.ibm.com \
--cc=brking@linux.vnet.ibm.com \
--cc=hare@suse.com \
--cc=hch@lst.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=jthumshirn@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=stable@vger.kernel.org \
/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