DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Min Hu (Connor)" <humin29@huawei.com>
To: Thomas Monjalon <thomas@monjalon.net>, <reshma.pattan@intel.com>,
	Maryam Tahhan <maryam.tahhan@intel.com>
Cc: <dev@dpdk.org>, <ferruh.yigit@intel.com>, <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] app/procinfo: add device registers dump
Date: Sat, 17 Jul 2021 10:16:56 +0800	[thread overview]
Message-ID: <f2953057-a591-2ff7-6499-2227413b628d@huawei.com> (raw)
In-Reply-To: <1780843.GLTCmdyZCW@thomas>

Hi, all,
	any comments for this patch?

在 2021/7/10 5:55, Thomas Monjalon 写道:
> 21/06/2021 04:17, Min Hu (Connor):
>> From: Chengchang Tang <tangchengchang@huawei.com>
>>
>> This patch add support for dump the device registers from a running
>> application. It can help developers locate the problem.
>>
>> Signed-off-by: Chengchang Tang <tangchengchang@huawei.com>
>> Signed-off-by: Min Hu (Connor) <humin29@huawei.com>
>> ---
>> v2:
>> * some logs are adjusted and error string are printed after
>> file operation fails.
> 
> Ping for review please.
> 
> 
> 
> .
> 

  reply	other threads:[~2021-07-17  2:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-25 13:02 [dpdk-dev] [PATCH] " Min Hu (Connor)
2021-05-19 10:16 ` Thomas Monjalon
2021-06-04 15:04 ` Pattan, Reshma
2021-06-05  3:15   ` Chengchang Tang
2021-06-10 16:25     ` Pattan, Reshma
2021-06-21  2:17 ` [dpdk-dev] [PATCH v2] " Min Hu (Connor)
2021-07-09 21:55   ` Thomas Monjalon
2021-07-17  2:16     ` Min Hu (Connor) [this message]
2021-07-17 17:51 ` [dpdk-dev] [PATCH] " Stephen Hemminger
2021-07-19  6:40   ` Chengchang Tang
2021-07-17 17:53 ` Stephen Hemminger
2021-07-19  7:00   ` Chengchang Tang
2021-07-22 10:58 ` [dpdk-dev] [PATCH v3] " Min Hu (Connor)
2021-07-29 14:14   ` Pattan, Reshma
2021-07-30 16:46     ` Thomas Monjalon

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=f2953057-a591-2ff7-6499-2227413b628d@huawei.com \
    --to=humin29@huawei.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=maryam.tahhan@intel.com \
    --cc=reshma.pattan@intel.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).