From: "John W. Linville" <linville@tuxdriver.com>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com, akpm@osdl.org,
jgarzik@pobox.com, marcelo.tosatti@cyclades.com
Subject: Re: [patch 2.4.28-pre3] 3c59x: resync with 2.6
Date: Fri, 8 Oct 2004 13:26:03 -0400 [thread overview]
Message-ID: <20041008132603.G14378@tuxdriver.com> (raw)
In-Reply-To: <20041008191324.J17999@flint.arm.linux.org.uk>; from rmk+lkml@arm.linux.org.uk on Fri, Oct 08, 2004 at 07:13:24PM +0100
On Fri, Oct 08, 2004 at 07:13:24PM +0100, Russell King wrote:
> On Fri, Oct 08, 2004 at 12:13:07PM -0400, John W. Linville wrote:
> > Backport of current 3c59x driver (minus EISA/sysfs stuff) from 2.6 to
> > 2.4. This should ease further maintenance in 2.4.
> > ---
> > I've been chasing some 3c59x driver problems on both 2.4.x and 2.6.x
> > kernels. The 3c59x driver was pretty far out of sync between the two
> > trees, so I thought it made sense to sync them back up.
>
> Ah, if someone's looking at the 3c59x driver then please look into the
> NWAY autonegotiation code - even maybe update it to use mii.c.
Russell,
If you can help to get my patches applied, then I'll be happy to look at
this for you... :-)
BTW, does this sound like the same issue:
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=75813
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2004-10-08 18:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 16:13 [patch 2.4.28-pre3] 3c59x: resync with 2.6 John W. Linville
2004-10-08 16:16 ` John W. Linville
2004-10-08 18:13 ` Russell King
2004-10-08 17:26 ` John W. Linville [this message]
2004-10-08 18:32 ` Jeff Garzik
2004-10-08 19:05 ` Jeff Garzik
2004-10-08 18:29 ` John W. Linville
2004-10-08 18:56 ` John W. Linville
2004-10-08 19:11 ` [patch 2.6.9-rc3] 3c59x: style change in vortex_ethtool_ops declaration John W. Linville
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=20041008132603.G14378@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=netdev@oss.sgi.com \
--cc=rmk+lkml@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.