From: Martin Dalecki <dalecki@evision-ventures.com>
To: Andre Hedrick <andre@linuxdiskcert.org>
Cc: Daniel Quinlan <quinlan@transmeta.com>,
linux-kernel@vger.kernel.org,
Marcelo Tosatti <marcelo@conectiva.com.br>,
Linus Torvalds <torvalds@transmeta.com>,
Dave Bogdanoff <bog@transmeta.com>
Subject: Re: [PATCH] Linux Secondary Slave IDE timings
Date: Tue, 26 Feb 2002 12:08:56 +0100 [thread overview]
Message-ID: <3C7B6CC8.3090509@evision-ventures.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10202260021200.14807-100000@master.linux-ide.org>
Andre Hedrick wrote:
> It is a valid and correct fix.
> There must have been a bug or something in an odd compiler, but the reason
> for the <> | order problem escapes me now.
> The verification came from a commumication I had with the author of the
> Intel programmer docs.
>
> I hope my comments do not kill the patch.
Certainly NOT. Thank's for confirmation.
prev parent reply other threads:[~2002-02-26 11:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 8:20 [PATCH] Linux Secondary Slave IDE timings Daniel Quinlan
2002-02-26 8:24 ` Andre Hedrick
2002-02-26 11:08 ` Martin Dalecki [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=3C7B6CC8.3090509@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=andre@linuxdiskcert.org \
--cc=bog@transmeta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=quinlan@transmeta.com \
--cc=torvalds@transmeta.com \
/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.