From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Guo, Jia" <jia.guo@intel.com>, "Xing, Beilei" <beilei.xing@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/i40e: fix link up failure issue
Date: Fri, 18 May 2018 13:16:51 +0000 [thread overview]
Message-ID: <039ED4275CED7440929022BC67E70611531B48DD@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1526609118-119241-1-git-send-email-jia.guo@intel.com>
> -----Original Message-----
> From: Zhang, Qi Z
> Sent: Friday, May 18, 2018 10:57 AM
> To: Guo, Jia <jia.guo@intel.com>; Xing, Beilei <beilei.xing@intel.com>
> Cc: dev@dpdk.org
> Subject: RE: [PATCH] net/i40e: fix link up failure issue
>
> > -----Original Message-----
> > From: Guo, Jia
> > Sent: Friday, May 18, 2018 10:05 AM
> > To: Zhang, Qi Z <qi.z.zhang@intel.com>; Xing, Beilei
> > <beilei.xing@intel.com>
> > Cc: dev@dpdk.org; Guo, Jia <jia.guo@intel.com>
> > Subject: [PATCH] net/i40e: fix link up failure issue
> >
> > In case of the known issue, that DPDK PHY config can't synchronous
> > with kernel driver and firmware, this will result of the nic can't
> > link up after rebind to the kernel driver. This patch propose to work
> > around it by don't config PHY and don't set link down when stop device.
> >
> > Fixes: 6e145fcc754b ("i40e: support autoneg or force link speed")
> >
> > Signed-off-by: Jeff Guo <jia.guo@intel.com>
>
> Acked-by: Qi Zhang <qi.z.zhang@intel.com>
Author agree to withdraw the patch, since kernel fix is in plan also this may impact link down experience, so
Nacked-by: Qi Zhang <qi.z.zhang@intel.com>
next prev parent reply other threads:[~2018-05-18 13:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 6:28 Jeff Guo
2018-05-16 14:43 ` Zhang, Qi Z
2018-05-17 6:07 ` Guo, Jia
2018-05-18 2:05 ` Jeff Guo
2018-05-18 2:56 ` Zhang, Qi Z
2018-05-18 13:16 ` Zhang, Qi Z [this message]
2018-05-18 2:02 Jeff Guo
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=039ED4275CED7440929022BC67E70611531B48DD@SHSMSX103.ccr.corp.intel.com \
--to=qi.z.zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jia.guo@intel.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).