From: Tejun Heo <htejun@gmail.com>
To: jgarzik@pobox.com, alan@lxorguk.ukuu.org.uk,
linux-ide@vger.kernel.org, htejun@gmail.com
Subject: [PATCHSET] hotplug polling, take 5
Date: Mon, 16 Oct 2006 07:37:26 +0900 [thread overview]
Message-ID: <11609518461142-git-send-email-htejun@gmail.com> (raw)
In-Reply-To:
Hello, all.
This is the fifth take of hotplug polling patchset. This take doesn't
contain any real change than rebasing over the current upstream[U].
PMP patchset will be posted soon on top of this patchset and I wanted
to avoid confusion by posting patchsets in order.
As the name implies, this patchset implements hotplug by polling.
hp-poll is used to
* Monitor ports EH gave up. When EH gives up on a port, it freezes
the port to protect the rest of the system from it. The user used
to have to issue manual scan to retry the port. hp-poll can monitor
such port and retry it when hotplug event is detected. This is also
used by PMP support.
* Support hotplug on controllers which can report hotplug conditions
but cannot raise interrupt.
Changes from the last take[L] are.
* updated to the current upstream
This patchset is also available in the following git tree.
http://htj.dyndns.org/git/?p=libata-tj.git;a=shortlog;h=hp-poll
git://htj.dyndns.org/libata-tj hp-poll
Thanks.
--
tejun
[U] da54f5fe54c7d75e2db7d17961fb36a8c28a8501
[L] http://article.gmane.org/gmane.linux.ide/13418
next reply other threads:[~2006-10-15 22:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-15 22:37 Tejun Heo [this message]
2006-10-15 22:37 ` [PATCH 1/3] libata: implement hotplug by polling Tejun Heo
2006-10-15 22:37 ` [PATCH 2/3] libata: add hp-poll support to controllers with hotplug interrutps Tejun Heo
2006-10-15 22:37 ` [PATCH 3/3] libata: add hp-poll support to controllers without hotplug interrupts Tejun Heo
2006-11-01 2:07 ` [PATCHSET] hotplug polling, take 5 Jeff Garzik
2006-11-01 3:02 ` Tejun Heo
2006-11-01 3:22 ` Jeff Garzik
2006-11-01 3:38 ` Tejun Heo
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=11609518461142-git-send-email-htejun@gmail.com \
--to=htejun@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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).