Netdev List
 help / color / mirror / Atom feed
From: Ben Hutchings <bhutchings@solarflare.com>
To: Somnath Kotur <somnath.kotur@emulex.com>
Cc: <netdev@vger.kernel.org>
Subject: Re: [PATCH ethtool] ethtool: Add string/define to display Port Type for Backplane Ethernet
Date: Fri, 2 Aug 2013 14:40:55 +0200	[thread overview]
Message-ID: <1375447255.11783.9.camel@deadeye.wl.decadent.org.uk> (raw)
In-Reply-To: <4f5874f0-845c-429e-8c14-fc948ed7a2e8@CMEXHTCAS1.ad.emulex.com>

On Fri, 2013-08-02 at 10:36 +0530, Somnath Kotur wrote:
> Signed-off-by: Somnath Kotur <somnath.kotur@emulex.com>
> ---
>  ethtool-copy.h |    1 +
>  ethtool.c      |    3 +++
>  2 files changed, 4 insertions(+), 0 deletions(-)
> 
> diff --git a/ethtool-copy.h b/ethtool-copy.h
> index b5515c2..33ff7d3 100644
> --- a/ethtool-copy.h
> +++ b/ethtool-copy.h
> @@ -989,6 +989,7 @@ enum ethtool_sfeatures_retval_bits {
>  #define PORT_FIBRE		0x03
>  #define PORT_BNC		0x04
>  #define PORT_DA			0x05
> +#define PORT_BACKPLANE		0x06
>  #define PORT_NONE		0xef
>  #define PORT_OTHER		0xff
>  

Needs to be updated in the kernel first.

> diff --git a/ethtool.c b/ethtool.c
> index b24b572..4db42b3 100644
> --- a/ethtool.c
> +++ b/ethtool.c
> @@ -625,6 +625,9 @@ static int dump_ecmd(struct ethtool_cmd *ep)
>  	case PORT_DA:
>  		fprintf(stdout, "Direct Attach Copper\n");
>  		break;
> +	case PORT_BACKPLANE:
> +		fprintf(stdout, "BackPlane\n");
> +		break;

Why the capital P?  I don't think I've seen it written that way before.

Ben.

>  	case PORT_NONE:
>  		fprintf(stdout, "None\n");
>  		break;

-- 
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.

      reply	other threads:[~2013-08-02 12:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-02  5:06 [PATCH ethtool] ethtool: Add string/define to display Port Type for Backplane Ethernet Somnath Kotur
2013-08-02 12:40 ` 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=1375447255.11783.9.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