patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>,
	Gowrishankar <gowrishankar.m@linux.vnet.ibm.com>
Cc: Adrien Mazarguil <adrien.mazarguil@6wind.com>,
	dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>,
	stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v4] net/mlx5: fix inconsistent link status query
Date: Mon, 31 Jul 2017 13:36:23 +0100	[thread overview]
Message-ID: <5e16e9a9-2c35-0bd6-cf1e-165d29e62f45@intel.com> (raw)
In-Reply-To: <20170725140111.GL2320@autoinstall.dev.6wind.com>

On 7/25/2017 3:01 PM, Nélio Laranjeiro wrote:
> On Tue, Jul 25, 2017 at 07:08:07PM +0530, Gowrishankar wrote:
>> From: Gowrishankar Muthukrishnan <gowrishankar.m@linux.vnet.ibm.com>
>>
>> ETHTOOL_GLINKSETTINGS ioctl call in mlx5 pmd returns inconsistent
>> link status due to which any application relying on it would not
>> function correctly.
>>
>> Fixes: 188408719888 ("net/mlx5: fix support for newer link speeds")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Gowrishankar Muthukrishnan <gowrishankar.m@linux.vnet.ibm.com>
> 
> Acked-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>

Applied to dpdk-next-net/master, thanks.

      reply	other threads:[~2017-07-31 12:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f4f3ef7e89eb42d415ad6cfe8e875d93b28a3547.1500359265.git.gowrishankar.m@linux.vnet.ibm.com>
2017-07-24 14:30 ` [dpdk-stable] [PATCH v2] net/mlx5: fix get link settings call for speed and duplex values Gowrishankar
2017-07-25  8:07   ` [dpdk-stable] [PATCH] net/mlx5: fix inconsistent link status query Gowrishankar
2017-07-25  9:41     ` Nélio Laranjeiro
2017-07-25 13:38     ` [dpdk-stable] [PATCH v4] " Gowrishankar
2017-07-25 14:01       ` Nélio Laranjeiro
2017-07-31 12:36         ` Ferruh Yigit [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=5e16e9a9-2c35-0bd6-cf1e-165d29e62f45@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=gowrishankar.m@linux.vnet.ibm.com \
    --cc=nelio.laranjeiro@6wind.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).