From: Aaron Wirtz <awirtz@novapointe.com>
To: sparclinux@vger.kernel.org
Subject: Re: future of drivers/fc4/
Date: Mon, 30 Aug 2004 18:01:24 +0000 [thread overview]
Message-ID: <200408301101.25149.awirtz@novapointe.com> (raw)
In-Reply-To: <412CB453.2050504@sms-softwaretechnik.de>
On Wednesday 25 August 2004 08:51, William Lee Irwin III wrote:
> I'm trying to arrange for a recovery from the changes between 2.2 and
> 2.4 as well as those between 2.4 and 2.6... this will not be trivial to
> do. Testing and help coding would be appreciated.
Let me know if I can help. Depending on work schedule and other stalled plans
for the machine, I may be able to help you test on an E3500. I would very
much like to see these drivers work.
-Aaron
next prev parent reply other threads:[~2004-08-30 18:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 15:46 future of drivers/fc4/ Matthias Schulz
2004-08-25 15:51 ` William Lee Irwin III
2004-08-25 18:34 ` C.Newport
2004-08-25 19:15 ` David S. Miller
2004-08-30 18:01 ` Aaron Wirtz [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-20 16:03 Christoph Hellwig
2004-06-20 16:03 ` Christoph Hellwig
2004-06-20 18:40 ` David S. Miller
2004-06-20 18:40 ` David S. Miller
2004-06-20 20:05 ` C.Newport
2004-06-20 20:05 ` C.Newport
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=200408301101.25149.awirtz@novapointe.com \
--to=awirtz@novapointe.com \
--cc=sparclinux@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.