From: willy@linux.intel.com (Matthew Wilcox)
Subject: Expected behaviour for device hang
Date: Fri, 17 May 2013 09:40:33 -0400 [thread overview]
Message-ID: <20130517134033.GP6057@linux.intel.com> (raw)
In-Reply-To: <alpine.LRH.2.03.1305151451090.7010@localhost.localdom>
On Wed, May 15, 2013@02:57:42PM -0600, Keith Busch wrote:
> As fas as "Cancelling I/O' over and over, that should have been fixed
> in this patch:
>
> http://merlin.infradead.org/pipermail/linux-nvme/2013-April/000215.html
>
> I thought that one was applied in the last merge, but looks like it was
> missed. :(
I thought so too. Sorry about that; applied now.
prev parent reply other threads:[~2013-05-17 13:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 20:17 Expected behaviour for device hang David.Darrington
2013-05-15 20:57 ` Keith Busch
2013-05-15 22:01 ` David.Darrington
2013-05-17 13:40 ` Matthew Wilcox [this message]
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=20130517134033.GP6057@linux.intel.com \
--to=willy@linux.intel.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;
as well as URLs for NNTP newsgroup(s).