From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Min Hu (Connor)" <humin29@huawei.com>, <dev@dpdk.org>
Subject: Re: [PATCH 0/9] dump device info
Date: Fri, 11 Feb 2022 18:04:34 +0000 [thread overview]
Message-ID: <6f4ae72e-16f5-2b5f-2a33-f3beff005f5d@intel.com> (raw)
In-Reply-To: <20220211044930.2449-1-humin29@huawei.com>
On 2/11/2022 4:49 AM, Min Hu (Connor) wrote:
> This patch set contains introduce dump API and a set of patches
> for hns3 dump implementation.
>
> Min Hu (Connor) (9):
> ethdev: introduce dump API
> net/hns3: dump device basic info
> net/hns3: dump device feature capability
> net/hns3: dump device MAC info
> net/hns3: dump queue info
> net/hns3: dump VLAN configuration info
> net/hns3: dump flow director basic info
> net/hns3: dump TM configuration info
> net/hns3: dump flow control info
>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2022-02-11 18:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 4:49 Min Hu (Connor)
2022-02-11 4:49 ` [PATCH v4 1/9] ethdev: introduce dump API Min Hu (Connor)
2022-02-11 10:41 ` Ferruh Yigit
2022-02-11 4:49 ` [PATCH 2/9] net/hns3: dump device basic info Min Hu (Connor)
2022-02-11 4:49 ` [PATCH 3/9] net/hns3: dump device feature capability Min Hu (Connor)
2022-02-11 4:49 ` [PATCH 4/9] net/hns3: dump device MAC info Min Hu (Connor)
2022-02-11 4:49 ` [PATCH 5/9] net/hns3: dump queue info Min Hu (Connor)
2022-02-11 4:49 ` [PATCH 6/9] net/hns3: dump VLAN configuration info Min Hu (Connor)
2022-02-11 4:49 ` [PATCH 7/9] net/hns3: dump flow director basic info Min Hu (Connor)
2022-02-11 4:49 ` [PATCH 8/9] net/hns3: dump TM configuration info Min Hu (Connor)
2022-02-11 4:49 ` [PATCH 9/9] net/hns3: dump flow control info Min Hu (Connor)
2022-02-11 18:04 ` 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=6f4ae72e-16f5-2b5f-2a33-f3beff005f5d@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=humin29@huawei.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).