From: "Pattan, Reshma" <reshma.pattan@intel.com>
To: "Min Hu (Connor)" <humin29@huawei.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
"stephen@networkplumber.org" <stephen@networkplumber.org>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"maryam.tahhan@intel.com" <maryam.tahhan@intel.com>
Subject: RE: [PATCH v2] app/procinfo: add devcie private info dump
Date: Wed, 25 May 2022 14:33:31 +0000 [thread overview]
Message-ID: <BYAPR11MB3366424A7080B71F01AC5635FFD69@BYAPR11MB3366.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220221022412.47258-1-humin29@huawei.com>
> -----Original Message-----
> From: Min Hu (Connor) <humin29@huawei.com>
> Subject: [PATCH v2] app/procinfo: add devcie private info dump
Typo: device*
> +static void
> +show_port_private_info(void)
> +{
> + int i;
> +
> + snprintf(bdr_str, MAX_STRING_LEN, " show - Port PMD Private ");
Better to have header message to be "Dump - Ports private information"
Looks ok to me.
Acked-by: Reshma Pattan <reshma.pattan@intel.com>
next prev parent reply other threads:[~2022-05-25 14:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-19 1:59 [PATCH] app/procinfo: add device private info dump Min Hu (Connor)
2022-02-20 1:04 ` Stephen Hemminger
2022-02-20 8:56 ` Thomas Monjalon
2022-02-21 2:26 ` Min Hu (Connor)
2022-02-21 17:04 ` Stephen Hemminger
2022-02-22 0:40 ` Min Hu (Connor)
2022-02-21 2:24 ` [PATCH v2] app/procinfo: add devcie " Min Hu (Connor)
2022-04-07 8:09 ` Min Hu (Connor)
2022-04-18 1:11 ` Min Hu (Connor)
2022-04-25 6:44 ` Min Hu (Connor)
2022-05-21 6:54 ` Min Hu (Connor)
2022-05-23 8:43 ` Ferruh Yigit
2022-05-25 14:33 ` Pattan, Reshma [this message]
2022-05-26 6:01 ` Min Hu (Connor)
2022-05-26 1:10 ` [PATCH v3] app/procinfo: add device " Min Hu (Connor)
2022-06-02 6:22 ` Min Hu (Connor)
2022-06-06 14:39 ` [PATCH v4] " Dongdong Liu
2022-06-13 12:45 ` Dongdong Liu
2022-06-13 12:51 ` Dongdong Liu
2022-06-26 15:50 ` Thomas Monjalon
2022-07-02 8:22 ` Dongdong Liu
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=BYAPR11MB3366424A7080B71F01AC5635FFD69@BYAPR11MB3366.namprd11.prod.outlook.com \
--to=reshma.pattan@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=humin29@huawei.com \
--cc=maryam.tahhan@intel.com \
--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 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.