patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Shahaf Shuler <shahafs@mellanox.com>
Cc: stable@dpdk.org, nelio.laranjeiro@6wind.com, adrien.mazarguil@6wind.com
Subject: Re: [dpdk-stable] [PATCH] net/mlx5: fix link status query
Date: Thu, 16 Feb 2017 12:40:02 +0800	[thread overview]
Message-ID: <20170216044002.GZ20916@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <1487146031-55218-1-git-send-email-shahafs@mellanox.com>

On Wed, Feb 15, 2017 at 10:07:11AM +0200, Shahaf Shuler wrote:
> [ backported from upstream commit 3a49ffe38a9508c57343719e5272e585c8dbd96c ]
> 
> Trying to query the link status through the new ETHTOOL_GLINKSETTINGS
> ioctl available since Linux 4.5 was always failing due to a kernel bug
> fixed since version 4.9.
> 
> This commit also addresses a common issue where the headers version used
> at compile time differs from that of the kernel on the target system, by
> always defining missing symbols and moving the kernel version check at run
> time.
> 
> Fixes: 188408719888 ("net/mlx5: fix support for newer link speeds")
> CC: stable@dpdk.org
> 
> Signed-off-by: Shahaf Shuler <shahafs@mellanox.com>
> Acked-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
> ---
> strangely i didn't had any conflicts. please let me know if you are encounter one.

My scripts first run "git format-patch", do some edits (like adding the
original commit info), then run "git am" to apply it. It failed.

I then tried "git cherry-pick" just now, as you stated, yes, it works.
Rerun "git am -3" shows that the conflict could be auto resolved.

So anyway, thanks for the backport! It's been queued to my local 16.11
branch, and it will be pushed to dpdk.org this Sat. if I got no
objections.

	--yliu

      reply	other threads:[~2017-02-16  4:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-15  8:07 Shahaf Shuler
2017-02-16  4:40 ` Yuanhan Liu [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=20170216044002.GZ20916@yliu-dev.sh.intel.com \
    --to=yuanhan.liu@linux.intel.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=nelio.laranjeiro@6wind.com \
    --cc=shahafs@mellanox.com \
    --cc=stable@dpdk.org \
    /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).