From: "Min Hu (Connor)" <humin29@huawei.com>
To: <dev@dpdk.org>
Cc: <ferruh.yigit@intel.com>
Subject: [dpdk-dev] [PATCH 0/4] bugfix for hns3 PMD
Date: Thu, 22 Apr 2021 09:55:48 +0800 [thread overview]
Message-ID: <1619056552-43937-1-git-send-email-humin29@huawei.com> (raw)
This patchset contains four bugfixes for hns3 PMD.
Chengwen Feng (4):
net/hns3: fix error mbx messages prompt errors
net/hns3: fix PF miss link status notify message
net/hns3: fix parse link fails code fail
net/hns3: delete unused macro and struct of mbx module
drivers/net/hns3/hns3_mbx.c | 18 +++++++++++-------
drivers/net/hns3/hns3_mbx.h | 10 ----------
2 files changed, 11 insertions(+), 17 deletions(-)
--
2.7.4
next reply other threads:[~2021-04-22 1:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 1:55 Min Hu (Connor) [this message]
2021-04-22 1:55 ` [dpdk-dev] [PATCH 1/4] net/hns3: fix error mbx messages prompt errors Min Hu (Connor)
2021-04-22 1:55 ` [dpdk-dev] [PATCH 2/4] net/hns3: fix PF miss link status notify message Min Hu (Connor)
2021-04-22 1:55 ` [dpdk-dev] [PATCH 3/4] net/hns3: fix parse link fails code fail Min Hu (Connor)
2021-04-26 12:26 ` Ferruh Yigit
2021-04-26 12:41 ` fengchengwen
2021-04-26 12:50 ` Ferruh Yigit
2021-04-26 13:20 ` fengchengwen
2021-04-26 13:42 ` [dpdk-dev] [PATCH v2] " Min Hu (Connor)
2021-04-27 11:11 ` Ferruh Yigit
2021-04-27 12:31 ` Min Hu (Connor)
2021-04-27 12:17 ` [dpdk-dev] [PATCH v3] " Min Hu (Connor)
2021-04-27 12:45 ` Ferruh Yigit
2021-04-27 13:03 ` Min Hu (Connor)
2021-04-27 13:19 ` Ferruh Yigit
2021-04-27 13:43 ` Min Hu (Connor)
2021-04-27 15:09 ` Ferruh Yigit
2021-04-22 1:55 ` [dpdk-dev] [PATCH 4/4] net/hns3: delete unused macro and struct of mbx module Min Hu (Connor)
2021-04-26 12:52 ` [dpdk-dev] [PATCH 0/4] bugfix for hns3 PMD Ferruh Yigit
2021-05-10 13:38 Min Hu (Connor)
2021-05-11 18:09 ` Ferruh Yigit
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=1619056552-43937-1-git-send-email-humin29@huawei.com \
--to=humin29@huawei.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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).