From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
Albert Lee <albertcc@tw.ibm.com>, Andy Warner <andyw@pobox.com>
Subject: Re: libata todo item: retry certain classes of errors
Date: Thu, 03 Feb 2005 17:16:53 +0000 [thread overview]
Message-ID: <1107450889.14847.148.camel@localhost.localdomain> (raw)
In-Reply-To: <42025E3B.8030302@pobox.com>
On Iau, 2005-02-03 at 17:24, Jeff Garzik wrote:
> > went away" error reports with the IDE layer (and they take forever).
>
> libata does a reset at the beginning of the probe...
Thats fine but resets when the drive is error handling get "interesting"
prev parent reply other threads:[~2005-02-03 18:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 4:33 libata todo item: retry certain classes of errors Jeff Garzik
2005-01-07 14:49 ` Alan Cox
2005-02-02 1:50 ` Jeff Garzik
2005-02-03 10:02 ` Alan Cox
2005-02-03 17:24 ` Jeff Garzik
2005-02-03 17:16 ` Alan Cox [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=1107450889.14847.148.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=albertcc@tw.ibm.com \
--cc=andyw@pobox.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).