From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Chen, Jing D" <jing.d.chen@intel.com>,
"Wang, Xiao W" <xiao.w.wang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH v2] net/fm10k: initialize link status in device start
Date: Thu, 22 Jun 2017 12:33:56 +0100 [thread overview]
Message-ID: <4813d667-1c31-8904-f8a3-a202fccb7e94@intel.com> (raw)
In-Reply-To: <4341B239C0EFF9468EE453F9E9F4604D3C66F6B1@shsmsx102.ccr.corp.intel.com>
On 6/22/2017 4:07 AM, Chen, Jing D wrote:
>
>
>> -----Original Message-----
>> From: Wang, Xiao W
>> Sent: Thursday, June 22, 2017 7:20 PM
>> To: Chen, Jing D <jing.d.chen@intel.com>
>> Cc: dev@dpdk.org; stable@dpdk.org; Wang, Xiao W <xiao.w.wang@intel.com>
>> Subject: [PATCH v2] net/fm10k: initialize link status in device start
>>
>> Fm10k host driver can't manage PHY directly and provides a fake link status by
>> always reporting LINK_UP. We should initialize link status in device start,
>> otherwise application will get LINK_DOWN status when LSC configured.
>>
>> Fixes: 9ae6068c86da ("fm10k: add dev start/stop")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Xiao Wang <xiao.w.wang@intel.com>
> Acked-by : Jing Chen <jing.d.chen@intel.com>
Applied to dpdk-next-net/master, thanks.
("__rte_unused" dropped from function prototype while applying)
prev parent reply other threads:[~2017-06-22 11:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 11:07 [dpdk-stable] [PATCH] " Xiao Wang
2017-06-21 2:35 ` Chen, Jing D
2017-06-22 2:31 ` Wang, Xiao W
2017-06-22 11:20 ` [dpdk-stable] [PATCH v2] " Xiao Wang
2017-06-22 3:07 ` Chen, Jing D
2017-06-22 11:33 ` 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=4813d667-1c31-8904-f8a3-a202fccb7e94@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=jing.d.chen@intel.com \
--cc=stable@dpdk.org \
--cc=xiao.w.wang@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).