From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] ethdev: fix link autonegotiation value
Date: Wed, 10 Jan 2018 20:54:56 +0000 [thread overview]
Message-ID: <26941444-afde-3ec6-93f3-48e8d67ad7d5@intel.com> (raw)
In-Reply-To: <20180105124707.602256c5@xeon-e3>
On 1/5/2018 8:47 PM, Stephen Hemminger wrote:
> On Fri, 5 Jan 2018 18:38:55 +0100
> Thomas Monjalon <thomas@monjalon.net> wrote:
>
>> There are 3 kind of link data in ethdev:
>> - capabilities (rte_eth_dev_info)
>> - configuration (rte_eth_conf)
>> - status (rte_eth_link)
>>
>> A bit-field is used for capabilities (rte_eth_dev_info.speed_capa) and
>> configuration (rte_eth_conf.link_speeds).
>> Bits are defined in ETH_LINK_SPEED_*.
>>
>> Some numerical (ETH_SPEED_NUM_*) and boolean (ETH_LINK_*) values
>> are used for the link status (rte_eth_link.*).
>>
>> There was a mistake in the comment of rte_eth_link.link_autoneg,
>> suggesting ETH_LINK_SPEED_[AUTONEG/FIXED] which are 0/1,
>> instead of ETH_LINK_[AUTONEG/FIXED] which are 1/0.
>>
>> The drivers are fixed to use ETH_LINK_[AUTONEG/FIXED].
>>
>> Fixes: 82113036e4e5 ("ethdev: redesign link speed config")
>>
>> Suggested-by: Andrew Rybchenko <arybchenko@solarflare.com>
>> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
>
> Thanks for clearing this up.
>
> Acked-by: Stephen Hemminger <stephen@networkplumber.org>
Applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2018-01-10 20:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 17:38 Thomas Monjalon
2018-01-05 20:47 ` Stephen Hemminger
2018-01-10 20:54 ` Ferruh Yigit [this message]
2018-01-08 12:31 ` Ferruh Yigit
2018-01-08 15:25 ` Thomas Monjalon
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=26941444-afde-3ec6-93f3-48e8d67ad7d5@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).