From: Jeff Garzik <jgarzik@pobox.com>
To: Hendrik Visage <hvisage@envisage.co.za>
Cc: Anton Starikov <A.Starikov@utwente.nl>, linux-raid@vger.kernel.org
Subject: Re: Support for PATA in Promise 378 driver
Date: Mon, 23 Feb 2004 20:21:00 -0500 [thread overview]
Message-ID: <403AA6FC.2080408@pobox.com> (raw)
In-Reply-To: <20040223133539.GO6255@hvs.envisage.co.za>
Hendrik Visage wrote:
> On Mon, Feb 23, 2004 at 02:16:36PM +0100, Anton Starikov wrote:
>>If now, why? Is there some religious reasons? ;)
>
>
> Elsewhere the answer is: Promise haven't provided the needed information yet.
I have the info (NDA, alas) but not the time, ATM.
Jeff
next prev parent reply other threads:[~2004-02-24 1:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 13:16 Support for PATA in Promise 378 driver Anton Starikov
2004-02-23 13:35 ` Hendrik Visage
2004-02-23 13:45 ` Anton Starikov
2004-02-27 18:56 ` Jeff Garzik
2004-02-27 19:45 ` Anton Starikov
2004-02-24 1:21 ` Jeff Garzik [this message]
2004-06-03 21:07 ` PATA in Promise 378 & troubles with Promise 378 Hendrik Visage
2004-02-24 1:20 ` Support for PATA in Promise 378 driver 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=403AA6FC.2080408@pobox.com \
--to=jgarzik@pobox.com \
--cc=A.Starikov@utwente.nl \
--cc=hvisage@envisage.co.za \
--cc=linux-raid@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).