From: "David S. Miller" <davem@davemloft.net>
To: mchan@broadcom.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 2/6] tg3: Add phy workaround
Date: Sat, 29 Apr 2006 18:57:28 -0700 (PDT) [thread overview]
Message-ID: <20060429.185728.67498626.davem@davemloft.net> (raw)
In-Reply-To: <1146267319.4780.15.camel@rh4>
From: "Michael Chan" <mchan@broadcom.com>
Date: Fri, 28 Apr 2006 16:35:19 -0700
> Add some PHY workaround code to reduce jitter on some PHYs.
>
> Signed-off-by: Michael Chan <mchan@broadcom.com>
Applied, thanks.
It really bugs me that all of this indirect addressing into
the DSP is done with magic addresses and register values. It
would be great to get some defined in tg3.h that documented
the DSP register set properly.
next prev parent reply other threads:[~2006-04-30 1:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 23:35 [PATCH 2/6] tg3: Add phy workaround Michael Chan
2006-04-30 1:57 ` David S. Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-01 4:45 Michael Chan
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=20060429.185728.67498626.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
/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).