From: Christoph Hellwig <hch@infradead.org>
To: Brian King <brking@linux.vnet.ibm.com>
Cc: Christoph Hellwig <hch@infradead.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-scsi@vger.kernel.org, wenxiong@linux.vnet.ibm.com
Subject: Re: [PATCH 1/2] ipr: Disable async aborts
Date: Thu, 30 Oct 2014 01:17:40 -0700 [thread overview]
Message-ID: <20141030081740.GA3194@infradead.org> (raw)
In-Reply-To: <54515918.4000107@linux.vnet.ibm.com>
On Wed, Oct 29, 2014 at 04:16:08PM -0500, Brian King wrote:
> I think we can likely drop the first in the series here. I've reverted it
> and have been running abort testing for a bit and haven't hit any issues.
> Unless I see anything overnight, I'll resend the second patch by itself and
> cc stable.
Thanks, please try to find a reviewer for it as well.
next prev parent reply other threads:[~2014-10-30 8:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 14:37 [PATCH 1/2] ipr: Disable async aborts Brian King
2014-10-27 14:50 ` James Bottomley
2014-10-28 8:47 ` Christoph Hellwig
2014-10-29 21:16 ` Brian King
2014-10-30 8:17 ` Christoph Hellwig [this message]
2014-10-28 13:58 ` Brian King
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=20141030081740.GA3194@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=brking@linux.vnet.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=wenxiong@linux.vnet.ibm.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