From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: John Treubig <jtreubig@hotmail.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: Error handling in LibATA
Date: Tue, 10 Jan 2006 23:15:16 +0000 [thread overview]
Message-ID: <1136934917.26976.4.camel@localhost.localdomain> (raw)
In-Reply-To: <BAY101-F102837A76FADACF6F37DBBDF250@phx.gbl>
On Maw, 2006-01-10 at 16:30 -0600, John Treubig wrote:
> I've traced the errors down to the fact that the errors are caught in
> libata-core.c (ata_qc_timeout). I'd like to put a call in libata-core.c
drivers/ide/* doesn't use libata. libata is used by the new PATA/SATA
drivers.
next prev parent reply other threads:[~2006-01-10 23:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-10 22:30 Error handling in LibATA John Treubig
2006-01-10 23:15 ` Alan Cox [this message]
2006-01-10 23:22 ` Douglas Gilbert
2006-01-11 2:07 ` Albert Lee
-- strict thread matches above, loose matches on Subject: below --
2006-01-11 15:30 John Treubig
2006-01-12 19:49 ` John Treubig
2006-01-13 5:45 ` Albert Lee
2006-01-13 15:41 ` John Treubig
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=1136934917.26976.4.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jtreubig@hotmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).