From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Chris Boot <bootc@bootc.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: libata PATA status report on 2.6.16-rc1-mm5
Date: Wed, 08 Feb 2006 17:26:29 +0000 [thread overview]
Message-ID: <1139419590.27721.9.camel@localhost.localdomain> (raw)
In-Reply-To: <43EA11F5.4000205@bootc.net>
On Mer, 2006-02-08 at 15:44 +0000, Chris Boot wrote:
> My next step will be to play with the CD drive. Any hints on
> stress-testing the drive? Obviously writing a CD then comparing to the
> ISO will be one step, but any others?
The PATA specific code is almost entirely in the setup stages. Once the
setup is done then (with the exception of early PIIX devices, radisys,
triflex and a couple of other oddities) there is no "new" code actually
being run.
Alan
next prev parent reply other threads:[~2006-02-08 17:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 9:58 libata PATA status report on 2.6.16-rc1-mm5 Chris Boot
2006-02-08 12:04 ` Alan Cox
2006-02-08 13:37 ` Chris Boot
2006-02-08 15:44 ` Chris Boot
2006-02-08 17:26 ` Alan Cox [this message]
2006-02-12 12:50 ` Chris Boot
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=1139419590.27721.9.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bootc@bootc.net \
--cc=linux-kernel@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