Netdev List
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: davem@davemloft.net,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	netdev@vger.kernel.org, gospo@redhat.com, sassmann@redhat.com
Subject: Re: [net-next 10/13] i40e: print full link message
Date: Fri, 06 Jun 2014 05:23:08 -0700	[thread overview]
Message-ID: <1402057388.3038.11.camel@joe-AO725> (raw)
In-Reply-To: <1402045462-10304-11-git-send-email-jeffrey.t.kirsher@intel.com>

On Fri, 2014-06-06 at 02:04 -0700, Jeff Kirsher wrote:
> The i40e driver should print link messages like all the
> other Intel Ethernet drivers.
[]
> diff --git a/drivers/net/ethernet/intel/i40e/i40e_main.c b/drivers/net/ethernet/intel/i40e/i40e_main.c
[]
> @@ -4135,6 +4135,54 @@ out:
>  	return err;
>  }
>  #endif /* CONFIG_I40E_DCB */
> +#define SPEED_SIZE 14
> +#define FC_SIZE 8
> +/**
> + * i40e_print_link_message - print link up or down
> + * @vsi: the VSI for which link needs a message
> + */
> +static void i40e_print_link_message(struct i40e_vsi *vsi, bool isup)
> +{
> +	char speed[SPEED_SIZE] = "Unknown";
> +	char fc[FC_SIZE] = "RX/TX";

It'd be better to use const char *,
smaller code, no unnecessary strncpys.

> +
> +	if (!isup) {
> +		netdev_info(vsi->netdev, "NIC Link is Down\n");
> +		return;
> +	}
> +
> +	switch (vsi->back->hw.phy.link_info.link_speed) {
> +	case I40E_LINK_SPEED_40GB:
> +		strncpy(speed, "40 Gbps", SPEED_SIZE);
> +		break;
> +	case I40E_LINK_SPEED_10GB:
> +		strncpy(speed, "10 Gbps", SPEED_SIZE);
> +		break;
> +	case I40E_LINK_SPEED_1GB:
> +		strncpy(speed, "1000 Mbps", SPEED_SIZE);
> +		break;
> +	default:
> +		break;
> +	}
> +
> +	switch (vsi->back->hw.fc.current_mode) {
> +	case I40E_FC_FULL:
> +		strncpy(fc, "RX/TX", FC_SIZE);
> +		break;
> +	case I40E_FC_TX_PAUSE:
> +		strncpy(fc, "TX", FC_SIZE);
> +		break;
> +	case I40E_FC_RX_PAUSE:
> +		strncpy(fc, "RX", FC_SIZE);
> +		break;
> +	default:
> +		strncpy(fc, "None", FC_SIZE);
> +		break;
> +	}
> +
> +	netdev_info(vsi->netdev, "NIC Link is Up %s Full Duplex, Flow Control: %s\n",
> +		    speed, fc);
> +}

  reply	other threads:[~2014-06-06 12:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-06  9:04 [net-next 00/13][pull request] Intel Wired LAN Driver Updates 2014-06-06 Jeff Kirsher
2014-06-06  9:04 ` [net-next 01/13] i40e: set lan_veb index Jeff Kirsher
2014-06-06  9:04 ` [net-next 02/13] i40e: add VEB stats to ethtool Jeff Kirsher
2014-06-06  9:04 ` [net-next 03/13] i40e: print message for pre-production hardware Jeff Kirsher
2014-06-06  9:04 ` [net-next 04/13] i40evf: make messages less dire Jeff Kirsher
2014-06-06 12:19   ` Joe Perches
2014-06-06 17:23     ` Williams, Mitch A
2014-06-06  9:04 ` [net-next 05/13] i40e/i40evf: check AQ register for valid data Jeff Kirsher
2014-06-06  9:04 ` [net-next 06/13] i40e/i40evf: add Tx pre queue disable function Jeff Kirsher
2014-06-06  9:04 ` [net-next 07/13] i40e: increase reset wait time Jeff Kirsher
2014-06-06  9:04 ` [net-next 08/13] i40e: add vsi x-cast stats Jeff Kirsher
2014-06-06  9:04 ` [net-next 09/13] i40e: add xcast stats for port Jeff Kirsher
2014-06-06  9:04 ` [net-next 10/13] i40e: print full link message Jeff Kirsher
2014-06-06 12:23   ` Joe Perches [this message]
2014-06-06  9:04 ` [net-next 11/13] i40e: don't remove HMC that doesn't exist Jeff Kirsher
2014-06-06  9:04 ` [net-next 12/13] i40e: remove irqs only when they are set up Jeff Kirsher
2014-06-06  9:04 ` [net-next 13/13] i40e/i40evf: Bump build version Jeff Kirsher
2014-06-06 20:04 ` [net-next 00/13][pull request] Intel Wired LAN Driver Updates 2014-06-06 David Miller

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=1402057388.3038.11.camel@joe-AO725 \
    --to=joe@perches.com \
    --cc=davem@davemloft.net \
    --cc=gospo@redhat.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=sassmann@redhat.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