From: Ye Xiaolong <xiaolong.ye@intel.com>
To: "Xu, Ting" <ting.xu@intel.com>
Cc: "Sun, GuinanX" <guinanx.sun@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"Yang, Qiming" <qiming.yang@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>
Subject: Re: [dpdk-dev] [PATCH 0/2] drivers/net: set fixed flag for exact link speed
Date: Mon, 6 Jan 2020 12:59:13 +0800 [thread overview]
Message-ID: <20200106045913.GB49980@intel.com> (raw)
In-Reply-To: <8C448DD570D7CD459EACDF44AB3869D7019597C4@SHSMSX106.ccr.corp.intel.com>
On 12/19, Xu, Ting wrote:
>
>
>> -----Original Message-----
>> From: dev <dev-bounces@dpdk.org> On Behalf Of Guinan Sun
>> Sent: Wednesday, December 4, 2019 12:59 AM
>> To: dev@dpdk.org
>> Cc: Lu, Wenzhuo <wenzhuo.lu@intel.com>; Yang, Qiming
>> <qiming.yang@intel.com>; Xing, Beilei <beilei.xing@intel.com>; Sun, GuinanX
>> <guinanx.sun@intel.com>
>> Subject: [dpdk-dev] [PATCH 0/2] drivers/net: set fixed flag for exact link speed
>>
>> Setting exact link speed makes sense if auto-negotiation is disabled. Fixed flag
>> is required to disable auto-negotiation.
>>
>> Guinan Sun (2):
>> net/i40e: set fixed flag for exact link speed
>> net/ixgbe: set fixed flag for exact link speed
>>
>> drivers/net/i40e/i40e_ethdev.c | 17 +++++++----------
>> drivers/net/ixgbe/ixgbe_ethdev.c | 20 +++++++-------------
>> 2 files changed, 14 insertions(+), 23 deletions(-)
>>
>> --
>> 2.17.1
>
>Reviewed-by: Ting Xu <ting.xu@intel.com>
>
Acked-by: Xiaolong Ye <xiaolong.ye@intel.com>
Applied to dpdk-next-net-intel, Thanks.
prev parent reply other threads:[~2020-01-06 5:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 16:59 [dpdk-dev] [PATCH 0/2] drivers/net: set fixed flag for exact link speed Guinan Sun
2019-12-03 16:59 ` [dpdk-dev] [PATCH 1/2] net/i40e: " Guinan Sun
2019-12-03 16:59 ` [dpdk-dev] [PATCH 2/2] net/ixgbe: " Guinan Sun
2019-12-19 5:27 ` [dpdk-dev] [PATCH 0/2] drivers/net: " Xu, Ting
2020-01-06 4:59 ` Ye Xiaolong [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=20200106045913.GB49980@intel.com \
--to=xiaolong.ye@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=guinanx.sun@intel.com \
--cc=qiming.yang@intel.com \
--cc=ting.xu@intel.com \
--cc=wenzhuo.lu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.