From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Li, Xiaoyun" <xiaoyun.li@intel.com>,
"Min Hu (Connor)" <humin29@huawei.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] app/testpmd: add link autoneg status display
Date: Mon, 19 Apr 2021 16:56:43 +0100 [thread overview]
Message-ID: <4759ace3-a788-3cc0-a5f4-e46292c26471@intel.com> (raw)
In-Reply-To: <DM4PR11MB55342B1BAEE07A11253A493F99499@DM4PR11MB5534.namprd11.prod.outlook.com>
On 4/19/2021 3:31 AM, Li, Xiaoyun wrote:
> Hi
>
>> -----Original Message-----
>> From: Min Hu (Connor) <humin29@huawei.com>
>> Sent: Thursday, April 15, 2021 14:45
>> To: dev@dpdk.org
>> Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; Li, Xiaoyun <xiaoyun.li@intel.com>
>> Subject: [PATCH] app/testpmd: add link autoneg status display
>>
>> From: Huisong Li <lihuisong@huawei.com>
>>
>> This patch adds link autoneg status display in port_infos_display().
>>
>> Signed-off-by: Huisong Li <lihuisong@huawei.com>
>> Signed-off-by: Min Hu (Connor) <humin29@huawei.com>
>> ---
>> app/test-pmd/config.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/app/test-pmd/config.c b/app/test-pmd/config.c index
>> 40b2b29..0dd6a6f 100644
>> --- a/app/test-pmd/config.c
>> +++ b/app/test-pmd/config.c
>> @@ -619,6 +619,8 @@ port_infos_display(portid_t port_id)
>> printf("Link speed: %s\n", rte_eth_link_speed_to_str(link.link_speed));
>> printf("Link duplex: %s\n", (link.link_duplex ==
>> ETH_LINK_FULL_DUPLEX) ?
>> ("full-duplex") : ("half-duplex"));
>> +printf("Autoneg status: %s\n", (link.link_autoneg ==
>> ETH_LINK_AUTONEG) ?
>> + ("On") : ("Off"));
>>
>> if (!rte_eth_dev_get_mtu(port_id, &mtu))
>> printf("MTU: %u\n", mtu);
>> --
>> 2.7.4
>
> Acked-by: Xiaoyun Li <xiaoyun.li@intel.com>
>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2021-04-19 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 6:45 Min Hu (Connor)
2021-04-19 2:31 ` Li, Xiaoyun
2021-04-19 15:56 ` 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=4759ace3-a788-3cc0-a5f4-e46292c26471@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=humin29@huawei.com \
--cc=xiaoyun.li@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).