From: Ajit Khaparde <ajit.khaparde@emulex.com>
To: <bhutchings@solarflare.com>
Cc: <netdev@vger.kernel.org>
Subject: [PATCH ethtool] ethtool: fix to display support for KX4 and KX PHY
Date: Wed, 6 Jun 2012 15:03:36 -0500 [thread overview]
Message-ID: <20120606200336.GA21620@akhaparde-VBox> (raw)
Signed-off-by: Ajit Khaparde <ajit.khaparde@emulex.com>
---
ethtool.c | 14 ++++++++++++++
1 files changed, 14 insertions(+), 0 deletions(-)
diff --git a/ethtool.c b/ethtool.c
index f18f611..546a43a 100644
--- a/ethtool.c
+++ b/ethtool.c
@@ -424,6 +424,13 @@ dump_link_caps(const char *prefix, const char *an_prefix, u32 mask)
if (mask & ADVERTISED_1000baseT_Full) {
did1++; fprintf(stdout, "1000baseT/Full ");
}
+ if (did1 && (mask & ADVERTISED_1000baseKX_Full)) {
+ fprintf(stdout, "\n");
+ fprintf(stdout, " %*s", indent, "");
+ }
+ if (mask & ADVERTISED_1000baseKX_Full) {
+ did1++; fprintf(stdout, "1000baseKX/Full ");
+ }
if (did1 && (mask & ADVERTISED_2500baseX_Full)) {
fprintf(stdout, "\n");
fprintf(stdout, " %*s", indent, "");
@@ -438,6 +445,13 @@ dump_link_caps(const char *prefix, const char *an_prefix, u32 mask)
if (mask & ADVERTISED_10000baseT_Full) {
did1++; fprintf(stdout, "10000baseT/Full ");
}
+ if (did1 && (mask & ADVERTISED_10000baseKX4_Full)) {
+ fprintf(stdout, "\n");
+ fprintf(stdout, " %*s", indent, "");
+ }
+ if (mask & ADVERTISED_10000baseKX4_Full) {
+ did1++; fprintf(stdout, "10000baseKX4/Full ");
+ }
if (did1 && (mask & ADVERTISED_20000baseMLD2_Full)) {
fprintf(stdout, "\n");
fprintf(stdout, " %*s", indent, "");
--
1.7.5.4
next reply other threads:[~2012-06-06 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 20:03 Ajit Khaparde [this message]
2012-06-08 17:23 ` [PATCH ethtool] ethtool: fix to display support for KX4 and KX PHY Ben Hutchings
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=20120606200336.GA21620@akhaparde-VBox \
--to=ajit.khaparde@emulex.com \
--cc=bhutchings@solarflare.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).