From: Jeff Garzik <jeff@garzik.org>
To: Nathaniel Case <ncase@xes-inc.com>
Cc: Andy Fleming <afleming@freescale.com>,
netdev@vger.kernel.org, galak@kernel.crashing.org
Subject: Re: [PATCH 1/2] PHYLIB: Add get_link ethtool helper function
Date: Sun, 11 Jun 2006 12:13:37 -0400 [thread overview]
Message-ID: <448C4131.3000504@garzik.org> (raw)
In-Reply-To: <1149551292.10700.47.camel@localhost.localdomain>
Nathaniel Case wrote:
> This adds a phy_ethtool_get_link() function along the same lines as
> phy_ethtool_gset(). This provides drivers utilizing PHYLIB an
> alternative to using ethtool_op_get_link(). This is more desirable
> since the "Link detected" field in ethtool would actually reflect the
> state of the PHY register.
>
> Patch depends on previous patch (0/2).
>
> Signed-off-by: Nate Case <ncase@xes-inc.com>
> Signed-off-by: Andy Fleming <afleming@freescale.com>
NAK, needs an EXPORT
next prev parent reply other threads:[~2006-06-11 16:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 23:48 [PATCH 1/2] PHYLIB: Add get_link ethtool helper function Nathaniel Case
2006-06-11 16:13 ` Jeff Garzik [this message]
2006-06-12 16:12 ` Nathaniel Case
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=448C4131.3000504@garzik.org \
--to=jeff@garzik.org \
--cc=afleming@freescale.com \
--cc=galak@kernel.crashing.org \
--cc=ncase@xes-inc.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).