DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Min Hu (Connor)" <humin29@huawei.com>,
	Dongdong Liu <liudongdong3@huawei.com>
Cc: dev@dpdk.org, stephen@networkplumber.org, ferruh.yigit@amd.com,
	reshma.pattan@intel.com, mtahhan@redhat.com,
	Maryam Tahhan <maryam.tahhan@intel.com>
Subject: Re: [PATCH v4] app/procinfo: add device private info dump
Date: Sun, 26 Jun 2022 17:50:38 +0200	[thread overview]
Message-ID: <5278982.anssfa2V6d@thomas> (raw)
In-Reply-To: <20220606143932.12772-1-liudongdong3@huawei.com>

06/06/2022 16:39, Dongdong Liu:
> From: "Min Hu (Connor)" <humin29@huawei.com>
> 
> This patch adds support for dump the device private info from a running
> application. It can help developers locate the problem.
> 
> Signed-off-by: Min Hu (Connor) <humin29@huawei.com>
> Signed-off-by: Dongdong Liu <liudongdong3@huawei.com>
> Acked-by: Reshma Pattan <reshma.pattan@intel.com>

Applied, thanks.

[...]
>  /**< Enable show port. */
>  static uint32_t enable_shw_port;
> +/**< Enable show port private info. */
> +static uint32_t enable_shw_port_priv;

That's very strange this file is using some (wrong) doxygen syntax.
I'll fix this one when applying.
A cleanup may be needed for other comments in the file.

>  /**< Enable show tm. */
>  static uint32_t enable_shw_tm;
>  /**< Enable show crypto. */




  parent reply	other threads:[~2022-06-26 15:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-19  1:59 [PATCH] " 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
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 [this message]
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=5278982.anssfa2V6d@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=humin29@huawei.com \
    --cc=liudongdong3@huawei.com \
    --cc=maryam.tahhan@intel.com \
    --cc=mtahhan@redhat.com \
    --cc=reshma.pattan@intel.com \
    --cc=stephen@networkplumber.org \
    /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).