From: Jeff Garzik <jeff@garzik.org>
To: Greg.Chandler@wellsfargo.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Interphase Tachyon drivers missing.
Date: Mon, 11 Dec 2006 13:03:07 -0500 [thread overview]
Message-ID: <457D9D5B.2080407@garzik.org> (raw)
In-Reply-To: <E8C008223DD5F64485DFBDF6D4B7F71D023BAAD3@msgswbmnmsp25.wellsfargo.com>
Greg.Chandler@wellsfargo.com wrote:
> I went to upgrade my kernel on a couple of boxes yesterday and noticed
> that the Interphase Tachyon chipset Fibre Channel driver was removed
> from the kernel. I think 2.6.1 was the last one it was still in. Was
> there a reason it was pulled?
> If not, do I have to volunteer to put it back in or can someone with
> more skill re-add it?
It was dropped because it was unmaintained, and quickly falling behind
mainline. If it's a maintained driver with an active userbase, we're
interested...
Jeff
next prev parent reply other threads:[~2006-12-11 18:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-11 17:03 Interphase Tachyon drivers missing Greg.Chandler
2006-12-11 18:03 ` Jeff Garzik [this message]
2006-12-13 9:14 ` Rolf Eike Beer
-- strict thread matches above, loose matches on Subject: below --
2006-12-11 18:22 Greg.Chandler
2006-12-13 16:51 Greg.Chandler
2006-12-14 7:27 ` Rolf Eike Beer
2006-12-14 8:11 ` Martin K. Petersen
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=457D9D5B.2080407@garzik.org \
--to=jeff@garzik.org \
--cc=Greg.Chandler@wellsfargo.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox