From: Roland Dreier <rdreier@cisco.com>
To: Tejun Heo <htejun@gmail.com>
Cc: marc.c.dionne@gmail.com, Petr Vandrovec <vandrove@vc.cvut.cz>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
Jeff Garzik <jeff@garzik.org>
Subject: Re: [PATCH #upstream-fixes] sata_nv: make hardreset return -EAGAIN on success
Date: Tue, 22 Apr 2008 20:24:53 -0700 [thread overview]
Message-ID: <adaej8xckxm.fsf@cisco.com> (raw)
In-Reply-To: <480EA97D.8080704@gmail.com> (Tejun Heo's message of "Wed, 23 Apr 2008 12:14:05 +0900")
> sata_nv hardreset can't classify but was left out while unifying
> follow-up SRST request mechanism[1]. This caused detection failures
> on those controllers. Fix it.
Yep, fixes my system too.
Tested-by: Roland Dreier <rolandd@cisco.com>
next prev parent reply other threads:[~2008-04-23 3:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 3:14 [PATCH #upstream-fixes] sata_nv: make hardreset return -EAGAIN on success Tejun Heo
2008-04-23 3:24 ` Roland Dreier [this message]
2008-04-23 10:44 ` Marc Dionne
2008-04-25 4:48 ` Jeff Garzik
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=adaej8xckxm.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=marc.c.dionne@gmail.com \
--cc=vandrove@vc.cvut.cz \
/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).