From: Bill Davidsen <davidsen@tmr.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: jgarzik@pobox.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, saw@saw.sw.com.sg
Subject: Re: [2.6 patch] the overdue eepro100 removal
Date: Mon, 02 Jul 2007 15:02:45 -0400 [thread overview]
Message-ID: <46894BD5.9080609@tmr.com> (raw)
In-Reply-To: <20070701202139.GM10869@stusta.de>
Adrian Bunk wrote:
> This patch contains the overdue removal of the eepro100 driver.
>
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
>
The hardware supported by this driver is still in use, thanks. It's
probably easier to leave the eepro100 driver in than find anyone who
wants to investigate why the other driver (e100? from memory) doesn't
work with some cards. As I recall this was suggested over a year ago and
it was decided to leave it in, all of the reasons for doing so still
seem valid. There really doesn't seem to be a benefit, it's not like
people are working night and day to support new cards for this chip.
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
next prev parent reply other threads:[~2007-07-02 19:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-01 20:21 [2.6 patch] the overdue eepro100 removal Adrian Bunk
2007-07-01 20:33 ` Kok, Auke
2007-07-01 21:51 ` Jeff Garzik
2007-07-02 19:02 ` Bill Davidsen [this message]
2007-07-02 21:45 ` Kok, Auke
2007-07-05 16:01 ` Bill Davidsen
2007-07-09 12:52 ` Adrian Bunk
2007-07-09 17:27 ` Bill Davidsen
2007-07-09 17:37 ` Kok, Auke
2007-07-09 17:53 ` Jeff Garzik
2007-07-09 17:52 ` Adrian Bunk
2007-07-09 19:38 ` Bill Davidsen
2007-07-09 20:43 ` Ian McDonald
-- strict thread matches above, loose matches on Subject: below --
2008-05-19 21:53 Adrian Bunk
2008-08-06 21:10 Adrian Bunk
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=46894BD5.9080609@tmr.com \
--to=davidsen@tmr.com \
--cc=bunk@stusta.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saw@saw.sw.com.sg \
/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).