| To: | Jeff Garzik <jgarzik@xxxxxxxxx> |
|---|---|
| Subject: | Re: linux-2.6.9 eepro100 warning |
| From: | Terje Kvernes <terjekv@xxxxxxxxxxx> |
| Date: | Mon, 25 Oct 2004 21:54:38 +0200 |
| Cc: | Seiichi Nakashima <nakasima@xxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, Netdev <netdev@xxxxxxxxxxx> |
| In-reply-to: | <417C9A4E.3030909@pobox.com> (Jeff Garzik's message of "Mon, 25 Oct 2004 02:16:46 -0400") |
| Organization: | The friends of mr. Tux |
| References: | <200410232313.AA00003@prism.kumin.ne.jp> <417C9A4E.3030909@pobox.com> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Gnus/5.110002 (No Gnus v0.2) Emacs/21.1 (gnu/linux) |
Jeff Garzik <jgarzik@xxxxxxxxx> 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? -- Terje |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [patch 5/5] aes-586-asm: small optimizations, akpm |
|---|---|
| Next by Date: | Re: 2.6.9 failed assertion in tcp_timer.c, Phil Oester |
| Previous by Thread: | Re: linux-2.6.9 eepro100 warning, Jeff Garzik |
| Next by Thread: | Re: linux-2.6.9 eepro100 warning, Jeff Garzik |
| Indexes: | [Date] [Thread] [Top] [All Lists] |