From: John Ronciak <john.ronciak@gmail.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Stephen Hemminger <shemminger@osdl.org>,
Vitaly Bordug <vbordug@ru.mvista.com>,
jgarzik@pobox.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 14:27:16 -0800 [thread overview]
Message-ID: <56a8daef0601171427s75894fid0f8c4f9e2b28e50@mail.gmail.com> (raw)
In-Reply-To: <20060117184834.GD19398@stusta.de>
We don't of any problems reported against e100 that have not been
talked about in this thread (in old ARCH types). I think the eepro100
driver should be removed from the config "just in case" but we are in
full support of the e100 driver and if somebody says that it's not
working on one of the different ARCHs we are willing to work with them
to get it fixed. The problem is that we don't have all these
different ARCH systems around to test against.
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.
--
Cheers,
John
next prev parent reply other threads:[~2006-01-17 22:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 18:18 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 [this message]
2006-01-18 0:32 ` John W. Linville
2006-01-18 0:36 ` Jeff Garzik
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=56a8daef0601171427s75894fid0f8c4f9e2b28e50@mail.gmail.com \
--to=john.ronciak@gmail.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 \
--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
all inboxes | Powered by JetHome®