From: Jeff Garzik <jgarzik@pobox.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: nforce2 keeps crashing with 2.4.27pre3
Date: Wed, 26 May 2004 13:22:11 -0400 [thread overview]
Message-ID: <40B4D243.5030500@pobox.com> (raw)
In-Reply-To: <20040526191619.B6244@electric-eye.fr.zoreil.com>
Francois Romieu wrote:
> Jeff Garzik <jgarzik@pobox.com> :
> [...]
>
>>Driver bugs... r8169 needs updating.
>
>
> Do you have a specific option in mind:
> - simple 2.6.6 backport (no napi nor ethtool support);
> - netdev backport (2.6.6 + napi)
> - new wave (2.6.6 + napi + ethtool/link/TBI rework)
I prefer to have the 2.4 and 2.6 drivers as close as possible to each
other, to reduce the maintenance burden.
If the mainline r8169.c looks stable, then I would take that source and
backport it to 2.4.x.
Jeff
next prev parent reply other threads:[~2004-05-26 17:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 15:56 nforce2 keeps crashing with 2.4.27pre3 Jens Kübler
2004-05-26 16:24 ` Jeff Garzik
2004-05-26 17:16 ` Francois Romieu
2004-05-26 17:22 ` Jeff Garzik [this message]
2004-05-26 20:47 ` r8169 backport for 2.4.27-pre3 (was: Re: nforce2 keeps crashing with 2.4.27pre3) Francois Romieu
2004-05-27 17:28 ` r8169 backport for 2.4.27-pre3 Jeff Garzik
2004-05-26 17:07 ` nforce2 keeps crashing with 2.4.27pre3 Francois Romieu
2004-05-27 11:01 ` Jens Kübler
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=40B4D243.5030500@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=romieu@fr.zoreil.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