From: "David S. Miller" <davem@redhat.com>
To: Arthur Kepner <akepner@sgi.com>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH] tg3 h/w flow control autoneg
Date: Tue, 25 May 2004 13:01:53 -0700 [thread overview]
Message-ID: <20040525130153.49af3d78.davem@redhat.com> (raw)
In-Reply-To: <Pine.SGI.4.56.0405251158550.9934718@neteng.engr.sgi.com>
On Tue, 25 May 2004 12:20:05 -0700
Arthur Kepner <akepner@sgi.com> wrote:
> The problem turned out to be that h/w flow control wasn't
> being used, even after that should have been autonegotiated.
> The attached patch (against 2.6.6) fixes that.
What an embarassing bug. Patch applied, good spotting Arthur.
next prev parent reply other threads:[~2004-05-25 20:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 7:26 [PATCH] fix BUG in tg3_tx Greg Banks
2004-05-24 7:40 ` David S. Miller
2004-05-24 8:04 ` Greg Banks
2004-05-24 17:06 ` David S. Miller
2004-05-25 1:04 ` Greg Banks
2004-05-25 17:51 ` David S. Miller
2004-05-25 19:20 ` [PATCH] tg3 h/w flow control autoneg Arthur Kepner
2004-05-25 20:01 ` David S. Miller [this message]
2004-05-26 0:12 ` [PATCH] fix BUG in tg3_tx Greg Banks
2004-05-25 17:52 ` David S. Miller
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=20040525130153.49af3d78.davem@redhat.com \
--to=davem@redhat.com \
--cc=akepner@sgi.com \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).