From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Iremonger, Bernard" <bernard.iremonger@intel.com>,
Viacheslav Ovsiienko <viacheslavo@mellanox.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v3] app/testpmd: fix show port info routine
Date: Wed, 17 Jul 2019 15:37:51 +0100 [thread overview]
Message-ID: <8053f098-9100-b085-5f7c-d92a1bd0d178@intel.com> (raw)
In-Reply-To: <8CEF83825BEC744B83065625E567D7C260DD086B@IRSMSX108.ger.corp.intel.com>
On 7/16/2019 11:44 AM, Iremonger, Bernard wrote:
>> -----Original Message-----
>> From: Viacheslav Ovsiienko [mailto:viacheslavo@mellanox.com]
>> Sent: Tuesday, July 16, 2019 11:35 AM
>> To: dev@dpdk.org
>> Cc: Iremonger, Bernard <bernard.iremonger@intel.com>; stable@dpdk.org
>> Subject: [PATCH v3] app/testpmd: fix show port info routine
>>
>> This patch updates "show port info [port_id]" command to display the
>> tx_desc_lim.nb_seg_max and tx_desc_lim.nb_mtu_seg_max fields of
>> rte_eth_dev_info structure.
>>
>> Fixes: 4fb7e803eb1a ("ethdev: add Tx preparation")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
>
> Acked-by: Bernard Iremonger <bernard.iremonger@intel.com>
>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2019-07-17 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 10:25 [dpdk-dev] [PATCH v2] app/testpmd: fix show port info routine Viacheslav Ovsiienko
2019-07-16 10:34 ` [dpdk-dev] [PATCH v3] " Viacheslav Ovsiienko
2019-07-16 10:44 ` Iremonger, Bernard
2019-07-17 14:37 ` 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=8053f098-9100-b085-5f7c-d92a1bd0d178@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=viacheslavo@mellanox.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).