From: Rick Hohensee <humbubba@smarty.smart.net>
To: linux-kernel@vger.kernel.org
Subject: Re: LANCE ethernet chip - ~24 drivers
Date: Tue, 31 Jul 2001 12:58:10 -0400 (EDT) [thread overview]
Message-ID: <200107311658.MAA03706@smarty.smart.net> (raw)
Jan-Benedict Glaw
>That are *many* drivers for at least *one* chip. For now, I'm
>working to get a serial keyboard running. However - having
>more than 20 drivers for one kind of device sucks a lot. So
One has to wonder. I was looking at 1.2.13 and there is mention of
splitting a driver, I forget which one, because there are two bits with
reversed sense in later versions of a card.
This raises a question about open source. How do you aknowledge code
removal? Given a system at some level of existing functionality, removing
code is one of the best things you can do for it, but it doesn't get your
name anywhere that sticks. Maybe Linux needs a linux/NO_MAINTENANCE .
Rick Hohensee
www.clienux.com
next reply other threads:[~2001-07-31 16:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-31 16:58 Rick Hohensee [this message]
2001-07-31 18:14 ` LANCE ethernet chip - ~24 drivers Horst von Brand
2001-08-01 8:39 ` Maciej W. Rozycki
[not found] <mailman.996536700.4319.linux-kernel2news@redhat.com>
2001-07-31 0:44 ` Pete Zaitcev
-- strict thread matches above, loose matches on Subject: below --
2001-07-30 23:42 Jan-Benedict Glaw
2001-08-01 21:55 ` 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=200107311658.MAA03706@smarty.smart.net \
--to=humbubba@smarty.smart.net \
--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