From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Linux-ide <linux-ide@vger.kernel.org>
Subject: EH progress summary
Date: Mon, 20 Feb 2006 12:40:35 +0900 [thread overview]
Message-ID: <43F93A33.1020809@gmail.com> (raw)
Hello, Jeff.
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. 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.
Thanks a lot. :-)
--
tejun
[1] http://article.gmane.org/gmane.linux.ide/7997
[2] http://article.gmane.org/gmane.linux.ide/8048
[3] http://article.gmane.org/gmane.linux.ide/8050
[4] http://article.gmane.org/gmane.linux.ide/8054
next reply other threads:[~2006-02-20 3:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 3:40 Tejun Heo [this message]
2006-02-20 8:11 ` EH progress summary Albert Lee
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=43F93A33.1020809@gmail.com \
--to=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).