netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: yoshfuji@linux-ipv6.org
Cc: jgarzik@pobox.com, nakasima@kumin.ne.jp,
	linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: linux-2.6.9 eepro100 warning
Date: Thu, 28 Oct 2004 00:36:15 -0400	[thread overview]
Message-ID: <4180773F.3060307@pobox.com> (raw)
In-Reply-To: <20041025.152749.00307602.yoshfuji@linux-ipv6.org>

YOSHIFUJI Hideaki / 吉藤英明 wrote:
> In article <417C9A4E.3030909@pobox.com> (at Mon, 25 Oct 2004 02:16:46 -0400), Jeff Garzik <jgarzik@pobox.com> says:
> 
> 
>>Note that eepro100 driver will be deleted soon.
> 
> 
> I'm afraid that e100 does not work well on some systems (e.g. my ThinkPad
> T30 on 2.4.x) while eepro100 does.
> (I also know there're systems which does not work well
> with eepro100 but e100.)
> 
> Has all of such kind of issues been solved?


My overall position is, -almost all- the issues have been solved in 
e100, so this should flush the last remaining ones out of the woodwork. 
  Otherwise nobody will ever notice much less test e100 on these various 
edge cases.

	Jeff

  parent reply	other threads:[~2004-10-28  4:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200410232313.AA00003@prism.kumin.ne.jp>
2004-10-25  6:16 ` linux-2.6.9 eepro100 warning Jeff Garzik
2004-10-25  6:25   ` Nick Piggin
2004-10-25  6:27   ` YOSHIFUJI Hideaki / 吉藤英明
2004-10-25  6:29     ` Jeff Garzik
2004-10-28  4:36     ` Jeff Garzik [this message]
2004-10-25 19:54   ` Terje Kvernes
2004-10-28  4:38     ` Jeff Garzik
2004-10-28 15:45       ` Terje Kvernes
2004-10-30  5:40         ` Seiichi Nakashima

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=4180773F.3060307@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nakasima@kumin.ne.jp \
    --cc=netdev@oss.sgi.com \
    --cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).