From: Jeff Garzik <jgarzik@pobox.com>
To: Terje Kvernes <terjekv@math.uio.no>
Cc: Seiichi Nakashima <nakasima@kumin.ne.jp>,
linux-kernel@vger.kernel.org, Netdev <netdev@oss.sgi.com>
Subject: Re: linux-2.6.9 eepro100 warning
Date: Thu, 28 Oct 2004 00:38:20 -0400 [thread overview]
Message-ID: <418077BC.10806@pobox.com> (raw)
In-Reply-To: <wxxr7nma801.fsf@nommo.uio.no>
Terje Kvernes wrote:
> Jeff Garzik <jgarzik@pobox.com> writes:
>
> [ ... ]
>
>
>>Note that eepro100 driver will be deleted soon.
>
>
> we have several systems where e100 produces netdev watchdog errors,
> while eepro100 works without problems. I can understand the desire
> to migrate, but what timeframe are we looking at? roughly
> translated, when do I _have_ to start help debugging the e100
> driver? ;-)
>
> I can do another attempt at rolling out the e100 driver, see what
> breaks, and try to report it around 2.6.1[01] or something like that
> if that helps?
If there are e100 problems, report them to the maintainers so we can get
them resolved ASAP...
INTEL PRO/100 ETHERNET SUPPORT
P: John Ronciak
M: john.ronciak@intel.com
P: Ganesh Venkatesan
M: ganesh.venkatesan@intel.com
P: Scott Feldman
M: scott.feldman@intel.com
W: http://sourceforge.net/projects/e1000/
S: Supported
(and of course netdev@oss.sgi.com as well)
next prev parent reply other threads:[~2004-10-28 4:38 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
2004-10-25 19:54 ` Terje Kvernes
2004-10-28 4:38 ` Jeff Garzik [this message]
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=418077BC.10806@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nakasima@kumin.ne.jp \
--cc=netdev@oss.sgi.com \
--cc=terjekv@math.uio.no \
/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).