From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <htejun@gmail.com>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: [PATCH] ahci: do not fail softreset if PHY reports no device
Date: Tue, 04 Apr 2006 08:44:48 -0400 [thread overview]
Message-ID: <44326A40.3040008@garzik.org> (raw)
In-Reply-To: <20060402165806.GO13172@htj.dyndns.org>
Tejun Heo wrote:
> All softreset methods are responsible for detecting device presence
> and succeed softreset in such cases. AHCI didn't use to check for
> device presence before proceeding with softreset and this caused
> unnecessary reset retrials during probing. This patch adds presence
> detection to AHCI softreset.
>
> Signed-off-by: Tejun Heo <htejun@gmail.com>
>
> ---
>
> This makes AHCI act like all other softresets and new EH already
> handles false successes properly. So, I think this should do the
> trick.
applied
prev parent reply other threads:[~2006-04-04 12:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-02 16:16 New probe code causes boot delay on empty ports Jeff Garzik
2006-04-02 16:49 ` Tejun Heo
2006-04-02 16:58 ` [PATCH] ahci: do not fail softreset if PHY reports no device Tejun Heo
2006-04-04 12:44 ` Jeff Garzik [this message]
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=44326A40.3040008@garzik.org \
--to=jeff@garzik.org \
--cc=htejun@gmail.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).