From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] IDE probe & waiting for busy
Date: Sun, 22 Sep 2002 01:01:08 -0400 [thread overview]
Message-ID: <3D8D4E94.8030707@mandrakesoft.com> (raw)
In-Reply-To: Pine.LNX.4.10.10209212150410.25090-100000@master.linux-ide.org
Andre Hedrick wrote:
> Ben,
>
> Catch Jeff and see if the execute diagnostics will solve the problem and
> if so we can extend the state machine path to cover the Apple mess.
>
> Thoughts?
> On Sat, 21 Sep 2002, Benjamin Herrenschmidt wrote:
>>If you prefer still running the execute diagnostics command for
>>probe, then feel free to implement it ;)
Ben, in fact I implemented it. :) I have been meaning to merge it into
the 2.4-ac stuff Alan/Andre are doing.
Jeff
next prev parent reply other threads:[~2002-09-22 4:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-21 15:28 [RFC] IDE probe & waiting for busy Benjamin Herrenschmidt
2002-09-22 4:52 ` Andre Hedrick
2002-09-22 5:01 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-22 9:48 Benjamin Herrenschmidt
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=3D8D4E94.8030707@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=andre@linux-ide.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.