From: Jeff Garzik <jgarzik@pobox.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: John Ronciak <john.ronciak@gmail.com>,
Adrian Bunk <bunk@stusta.de>,
Stephen Hemminger <shemminger@osdl.org>,
Vitaly Bordug <vbordug@ru.mvista.com>,
saw@saw.sw.com.sg, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] remove drivers/net/eepro100.c
Date: Tue, 17 Jan 2006 19:36:02 -0500 [thread overview]
Message-ID: <43CD8D72.6040501@pobox.com> (raw)
In-Reply-To: <20060118003232.GA28965@tuxdriver.com>
John W. Linville wrote:
> On Tue, Jan 17, 2006 at 02:27:16PM -0800, John Ronciak wrote:
>
>
>>Another thing is that removal of the driver (or disabling the config)
>>will hopefully force the issue in that people with these ARCHs will
>>use the e100 and if they have problems we can get them fixed in the
>>e100 driver. At this point nobody seems to be able to define a "real"
>>problem other than talking about it.
Someone should send me a patch that adds eepro100 to the feature-removal
doc.
jeff
next prev parent reply other threads:[~2006-01-18 0:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 18:18 [RFC: 2.6 patch] remove drivers/net/eepro100.c Adrian Bunk
2006-01-05 18:57 ` Jeff Garzik
2006-01-05 21:04 ` Lennert Buytenhek
2006-01-15 0:43 ` Adrian Bunk
2006-01-15 13:19 ` Vitaly Bordug
2006-01-16 0:03 ` Stephen Hemminger
2006-01-17 18:48 ` Adrian Bunk
2006-01-17 22:27 ` John Ronciak
2006-01-18 0:32 ` John W. Linville
2006-01-18 0:36 ` Jeff Garzik [this message]
2006-01-18 7:41 ` [2.6 patch] schedule eepro100.c for removal Adrian Bunk
2006-01-18 10:34 ` [RFC: 2.6 patch] remove drivers/net/eepro100.c Vitaly Bordug
2006-01-16 0:08 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2005-11-18 3:33 Adrian Bunk
2005-11-18 9:01 ` Russell King
2005-11-18 9:08 ` David S. Miller
2005-11-18 16:12 ` Jeff Garzik
2005-11-18 16:32 ` Russell King
2005-11-19 20:34 ` Adrian Bunk
2005-11-23 22:15 ` Russell King
2005-11-23 22:24 ` Russell King
2005-11-24 10:30 ` Catalin Marinas
2005-11-23 22:39 ` David S. Miller
2005-11-23 22:53 ` Russell King
2005-11-23 23:01 ` David S. Miller
2005-11-18 17:04 ` Tim Schmielau
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=43CD8D72.6040501@pobox.com \
--to=jgarzik@pobox.com \
--cc=bunk@stusta.de \
--cc=john.ronciak@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=saw@saw.sw.com.sg \
--cc=shemminger@osdl.org \
--cc=vbordug@ru.mvista.com \
/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).