From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: emilne@redhat.com
Cc: linux-scsi@vger.kernel.org, djeffery@redhat.com
Subject: Re: [PATCH] sd: medium access timeout counter fails to reset
Date: Thu, 17 Apr 2014 15:23:50 -0400 [thread overview]
Message-ID: <yq1tx9rep4p.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <1397490613.3832.20.camel@localhost.localdomain> (Ewan Milne's message of "Mon, 14 Apr 2014 11:50:13 -0400")
>>>>> "Ewan" == Ewan Milne <emilne@redhat.com> writes:
Ewan> Is there some reason why this patch was never accepted? David
Ewan> posted it a couple of times last year and Martin ack'ed it, but I
Ewan> don't see it in your tree, and I don't see any other comments on
Ewan> it.
I still don't have any objections.
FWIW, the reason my patch didn't handle the recovery scenario is that
the devices I originally wrote it for never came back (irreversibly
stuck head assembly or dead FTL).
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2014-04-17 19:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 15:08 [PATCH] sd: medium access timeout counter fails to reset David Jeffery
2014-04-14 15:50 ` Ewan Milne
2014-04-17 19:23 ` Martin K. Petersen [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=yq1tx9rep4p.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=djeffery@redhat.com \
--cc=emilne@redhat.com \
--cc=linux-scsi@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