From: Jeff Garzik <jeff@garzik.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Alan <alan@lxorguk.ukuu.org.uk>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org
Subject: Re: [PATCH] libata: Cable detection fixes
Date: Thu, 01 Mar 2007 20:33:17 -0500 [thread overview]
Message-ID: <45E77EDD.3010205@garzik.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0703011723270.12485@woody.linux-foundation.org>
Linus Torvalds wrote:
>
> On Thu, 1 Mar 2007, Alan wrote:
>> The patch switches the identify order so that we can do the drive side
>> detection correctly.
>>
>> Secondly we add a ->cable_detect() method called after the identify
>> sequence which allows a host to do host side detection at this point
>> should it wish, or to modify the results of the drive side identify.
>
> Alan, sign-offs?
>
> Jeff, should I just expect to get these things through you?
See my reply, which passed yours in-flight :)
I'm OK with all the changes, but ->cable_detect (and _nice_ cleanups)
does not seem like 2.6.21-rc bugfix material to me.
We definitely want the IDENTIFY ordering changes, though we'll also want
that passed through at least one more 2.6.21-rcX release before
confidence appears.
That little change, buried in the middle of Alan's patch, changes the
probing order for a /lot/ of devices, possibly millions, when you
consider that it changes behavior of ata_piix (Intel SATA) as well as
all the not-yet-default PATA controllers.
A wanted fix, but something that definitely wants a lot of public
testing before 2.6.21 release.
Jeff
next prev parent reply other threads:[~2007-03-02 1:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 17:30 [PATCH] libata: Cable detection fixes Alan
2007-03-02 1:24 ` Linus Torvalds
2007-03-02 1:33 ` Jeff Garzik [this message]
2007-03-02 6:35 ` Michal Jaegermann
2007-03-02 12:52 ` Alan Cox
2007-03-02 1:26 ` Jeff Garzik
2007-03-02 12:45 ` Alan Cox
2007-03-02 22:50 ` Jeff Garzik
2007-03-02 22:48 ` Jeff Garzik
2007-03-03 19:35 ` Paul Rolland
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=45E77EDD.3010205@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).