DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shahaf Shuler <shahafs@mellanox.com>
To: "Shahaf Shuler" <shahafs@mellanox.com>,
	"Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>,
	"Adrien Mazarguil" <adrien.mazarguil@6wind.com>,
	"Yongseok Koh" <yskoh@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 1/2] net/mlx5: fix ethtool link setting call	order
Date: Thu, 3 May 2018 05:51:21 +0000	[thread overview]
Message-ID: <DB7PR05MB44266911AC6CA15565E4FA64C3870@DB7PR05MB4426.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <421987dcb5779584a1c880a0a74c0eb245cbbfb2.1525168586.git.shahafs@mellanox.com>

Tuesday, May 1, 2018 12:59 PM, Shahaf Shuler:
> Subject: [dpdk-dev] [PATCH v2 1/2] net/mlx5: fix ethtool link setting call
> order
> 
> According to ethtool_link_setting API recommendation
> ETHTOOL_GLINKSETTINGS should be called before ETHTOOL_GSET as the
> later one deprecated.
> 
> Fixes: f47ba80080ab ("net/mlx5: remove kernel version check")
> 
> Signed-off-by: Shahaf Shuler <shahafs@mellanox.com>
> Acked-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>

Series applied to next-net-mlx, thanks. 

  reply	other threads:[~2018-05-03  5:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-29 18:03 [dpdk-dev] [PATCH " Shahaf Shuler
2018-04-29 18:03 ` [dpdk-dev] [PATCH 2/2] net/mlx5: add Rx and Tx tuning parameters Shahaf Shuler
2018-04-30  7:07   ` Nélio Laranjeiro
2018-04-30  7:08 ` [dpdk-dev] [PATCH 1/2] net/mlx5: fix ethtool link setting call order Nélio Laranjeiro
2018-05-01  9:58 ` [dpdk-dev] [PATCH v2 " Shahaf Shuler
2018-05-03  5:51   ` Shahaf Shuler [this message]
2018-05-01  9:58 ` [dpdk-dev] [PATCH v2 2/2] net/mlx5: add Rx and Tx tuning parameters Shahaf Shuler
2018-05-02  6:40   ` Nélio Laranjeiro

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=DB7PR05MB44266911AC6CA15565E4FA64C3870@DB7PR05MB4426.eurprd05.prod.outlook.com \
    --to=shahafs@mellanox.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=nelio.laranjeiro@6wind.com \
    --cc=yskoh@mellanox.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;
as well as URLs for NNTP newsgroup(s).