From: Vitaly Bordug <vbordug@ru.mvista.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: 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: Sun, 15 Jan 2006 16:19:58 +0300 [thread overview]
Message-ID: <20060115161958.07e3c7f1@vitb.dev.rtsoft.ru> (raw)
In-Reply-To: <20060105181826.GD12313@stusta.de>
On Thu, 5 Jan 2006 19:18:26 +0100
Adrian Bunk <bunk@stusta.de> wrote:
> This patch removes the obsolete drivers/net/eepro100.c driver.
>
> Is there any known problem in e100 still preventing us from removing
> this driver (it seems noone was able anymore to verify the ARM problem)?
>
I think I am recalling some problems on ppc82xx, when e100 was stuck on startup,
and eepro100 worked just fine.
Even if the patch below will be scheduled for application, we need to set up enough time
for approval that e100 will be fine for all the up-to-date hw; or it should be fixed/updated before eepro100 removal.
>
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
>
>
--
Sincerely,
Vitaly
next prev parent reply other threads:[~2006-01-15 13:19 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 [this message]
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
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=20060115161958.07e3c7f1@vitb.dev.rtsoft.ru \
--to=vbordug@ru.mvista.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).