From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Min Hu (Connor)" <humin29@huawei.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/7] features and bugfix for hns3 PMD
Date: Tue, 20 Apr 2021 01:42:45 +0100 [thread overview]
Message-ID: <cc193683-e685-b66f-0320-73da26fe7513@intel.com> (raw)
In-Reply-To: <1618653299-40380-1-git-send-email-humin29@huawei.com>
On 4/17/2021 10:54 AM, Min Hu (Connor) wrote:
> This patchset contains 2 features and 5 bugfixes.
>
> Chengwen Feng (3):
> net/hns3: check max SIMD bitwidth
> net/hns3: Rx vector add compile-time verify
> net/hns3: fix FDIR lock bug
>
> Huisong Li (4):
> net/hns3: remove redundant code about mbx
> net/hns3: fix the check for DCB mode
> net/hns3: fix the check for VMDq mode
> net/hns3: move the link speeds check to dev configure
>
Except 1/7,
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2021-04-20 0:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-17 9:54 [dpdk-dev] [PATCH 0/7] features and bugfix for hns3 PMD Min Hu (Connor)
2021-04-17 9:54 ` [dpdk-dev] [PATCH 1/7] net/hns3: check max SIMD bitwidth Min Hu (Connor)
2021-04-20 0:16 ` Ferruh Yigit
2021-04-17 9:54 ` [dpdk-dev] [PATCH 2/7] net/hns3: Rx vector add compile-time verify Min Hu (Connor)
2021-04-17 9:54 ` [dpdk-dev] [PATCH 3/7] net/hns3: remove redundant code about mbx Min Hu (Connor)
2021-04-17 9:54 ` [dpdk-dev] [PATCH 4/7] net/hns3: fix the check for DCB mode Min Hu (Connor)
2021-04-17 9:54 ` [dpdk-dev] [PATCH 5/7] net/hns3: fix the check for VMDq mode Min Hu (Connor)
2021-04-17 9:54 ` [dpdk-dev] [PATCH 6/7] net/hns3: fix FDIR lock bug Min Hu (Connor)
2021-04-17 9:54 ` [dpdk-dev] [PATCH 7/7] net/hns3: move the link speeds check to dev configure Min Hu (Connor)
2021-04-20 0:42 ` 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=cc193683-e685-b66f-0320-73da26fe7513@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 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.