From: Albert Lee <albertcc@tw.ibm.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, Linux-ide <linux-ide@vger.kernel.org>
Subject: Re: EH progress summary
Date: Mon, 20 Feb 2006 16:11:57 +0800 [thread overview]
Message-ID: <43F979CD.2060307@tw.ibm.com> (raw)
In-Reply-To: <43F93A33.1020809@gmail.com>
Hi Tejun:
>
> I think we're half-way through the EH changes. New reset mechanism and
> most of config reorganization are in tree. Currently, the patches which
> are waiting for your review are...
>
> [1] libata: rename ata_dev_id_[c_]string()
> [2] libata: reorganize ata_dev_identify() (7 patches)
> [3] libata: implement and use ata_dev_revalidate() (4 patches)
>
> Once these revalidation changes make into tree, I'll submit
> ata_set_mode() changes (I've submitted the first patchset of this but
> Alan had a valid objection. I agreed and dropped that one.[4])
>
> After ata_set_mode() changes are complete, the real EH changes will be
> submitted including error recording (to determine whether speed down is
> necessary) and all the recovery actions.
Will PATA speed down be supported?
e.g. udma133 => udma100 => udma66 => udma33 => pio ...
> I haven't splitted these yet
> but I guess it will be three or four patchsets.
>
> And after that, Jens' NCQ work can be integrated over it. The code
> required to implement NCQ is actually quite small. It will probably
> take only one patchset of about three to five patches.
>
> So, this is where we stand. I hope we can get new EH up and working soon.
>
>
Albert
next prev parent reply other threads:[~2006-02-20 8:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 3:40 EH progress summary Tejun Heo
2006-02-20 8:11 ` Albert Lee [this message]
2006-02-20 8:19 ` Tejun Heo
2006-02-20 8:27 ` Albert Lee
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=43F979CD.2060307@tw.ibm.com \
--to=albertcc@tw.ibm.com \
--cc=albertl@mail.com \
--cc=htejun@gmail.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).