From: "Wu, Jingjing" <jingjing.wu@intel.com>
To: "Guo, Jia" <jia.guo@intel.com>, "Xing, Beilei" <beilei.xing@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH v2] net/i40e: fix link down and negotiation issue
Date: Fri, 21 Jul 2017 06:33:14 +0000 [thread overview]
Message-ID: <9BB6961774997848B5B42BEC655768F810DCDA84@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1500606424-83169-1-git-send-email-jia.guo@intel.com>
> -----Original Message-----
> From: Guo, Jia
> Sent: Friday, July 21, 2017 11:07 AM
> To: Xing, Beilei <beilei.xing@intel.com>; Wu, Jingjing <jingjing.wu@intel.com>
> Cc: dev@dpdk.org; Guo, Jia <jia.guo@intel.com>; stable@dpdk.org
> Subject: [PATCH v2] net/i40e: fix link down and negotiation issue
>
> Enable the functions set link down and set link up in i40e by check phy_type,
> and fix the issue of auto negotiation failed in XXV710 when bind kernel driver
> after unbind from dpdk driver by modify the speed setting distinguish from set
> link up and down. With this fix, if unbind dpdk to bind kernel driver, no need to
> set auto negotiation and ifconfi up anymore, remove the part from doc.
>
> Fixes: ca7e599d4506 ("net/i40e: fix link management")
> Fixes: 2f1e22817420 ("i40e: skip link control as firmware workaround")
> Fixes: 6e145fcc754b ("i40e: support autoneg or force link speed")
> Signed-off-by: Jeff Guo <jia.guo@intel.com>
Acked-by: Jingjing Wu <jingjing.wu@intel.com>
> ---
> v2->v1: fix comment error and redefine variable
> ---
> doc/guides/nics/i40e.rst | 10 ----------
> drivers/net/i40e/i40e_ethdev.c | 34 ++++++++++++++++++++++------------
> 2 files changed, 22 insertions(+), 22 deletions(-)
>
next prev parent reply other threads:[~2017-07-21 6:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1500540302-84503-1-git-send-email-jia.guo@intel.com>
2017-07-21 3:07 ` Jeff Guo
2017-07-21 6:33 ` Wu, Jingjing [this message]
2017-07-21 9:06 ` Ferruh Yigit
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=9BB6961774997848B5B42BEC655768F810DCDA84@SHSMSX103.ccr.corp.intel.com \
--to=jingjing.wu@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jia.guo@intel.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).