From: Ben Hutchings <bhutchings@solarflare.com>
To: Somnath Kotur <somnath.kotur@emulex.com>
Cc: <netdev@vger.kernel.org>
Subject: Re: [PATCH ethtool]: Add strings to display Supported Ports for Backplane Ethernet
Date: Thu, 8 Aug 2013 20:27:30 +0200 [thread overview]
Message-ID: <1375986450.2853.54.camel@deadeye.wl.decadent.org.uk> (raw)
In-Reply-To: <ac83fc1a-a967-4035-bfed-a8deff029ace@CMEXHTCAS2.ad.emulex.com>
On Thu, 2013-08-01 at 17:39 +0530, Somnath Kotur wrote:
> Signed-off-by: Somnath Kotur <somnath.kotur@emulex.com>
> ---
> ethtool.c | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/ethtool.c b/ethtool.c
> index 3544f0e..b24b572 100644
> --- a/ethtool.c
> +++ b/ethtool.c
> @@ -485,6 +485,9 @@ static void dump_supported(struct ethtool_cmd *ep)
> fprintf(stdout, "MII ");
> if (mask & SUPPORTED_FIBRE)
> fprintf(stdout, "FIBRE ");
> + if ((mask & SUPPORTED_10000baseKR_Full) ||
> + (mask & SUPPORTED_10000baseKX4_Full))
> + fprintf(stdout, "BACKPLANE ");
> fprintf(stdout, "]\n");
>
> dump_link_caps("Supported", "Supports", mask, 0);
No, I don't think so. This is redundant information. It's also
pointless to add any new port types to the advertised and supported
masks unless we have hardware that can switch port type at run-time like
some old 10M boards.
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
prev parent reply other threads:[~2013-08-08 18:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 12:09 [PATCH ethtool]: Add strings to display Supported Ports for Backplane Ethernet Somnath Kotur
2013-08-08 18:27 ` Ben Hutchings [this message]
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=1375986450.2853.54.camel@deadeye.wl.decadent.org.uk \
--to=bhutchings@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=somnath.kotur@emulex.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