From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Min Hu (Connor)" <humin29@huawei.com>, dev@dpdk.org
Cc: konstantin.ananyev@intel.com, thomas@monjalon.net,
arybchenko@solarflare.com, linuxarm@huawei.com
Subject: Re: [dpdk-dev] [PATCH] app/testpmd: fix transmission from speed to str
Date: Fri, 9 Oct 2020 12:05:32 +0100 [thread overview]
Message-ID: <88f47e57-9043-8e0c-7e8c-c3eada366294@intel.com> (raw)
In-Reply-To: <1602215119-64740-1-git-send-email-humin29@huawei.com>
On 10/9/2020 4:45 AM, Min Hu (Connor) wrote:
> This patch uses a new 'rte_eth_link_speed_to_str()' API in the
> ethdev which enables removing above global 'eth_speed_name' array [1].
>
> Fixes: 466c55e4d85b ("app/testpmd: add FEC command")
>
> Signed-off-by: Min Hu (Connor) <humin29@huawei.com>
>
Squashed into relevant commit in next-net, thanks.
prev parent reply other threads:[~2020-10-09 11:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 3:45 Min Hu (Connor)
2020-10-09 11:05 ` 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=88f47e57-9043-8e0c-7e8c-c3eada366294@intel.com \
--to=ferruh.yigit@intel.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=humin29@huawei.com \
--cc=konstantin.ananyev@intel.com \
--cc=linuxarm@huawei.com \
--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).