From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Dongdong Liu <liudongdong3@huawei.com>,
dev@dpdk.org, ferruh.yigit@amd.com, thomas@monjalon.net
Cc: stable@dpdk.org, fengchengwen@huawei.com,
yisen.zhuang@huawei.com, lihuisong@huawei.com,
haijie1@huawei.com
Subject: Re: [PATCH 00/19] some bugfixes and clean code for hns3 - part2
Date: Wed, 5 Oct 2022 09:18:04 +0300 [thread overview]
Message-ID: <41f31c7b-1139-3519-dbea-5bf66019b5c3@oktetlabs.ru> (raw)
In-Reply-To: <20220930072220.20753-1-liudongdong3@huawei.com>
On 9/30/22 10:22, Dongdong Liu wrote:
> This patchset include some bugfixes and clean code for hns3.
> This patchset is based on the patchset [1] that have been sent out
> before. Depend on [1] applied first.
>
> [1]: [PATCH RESEND 00/13] some bugfixes and clean code for hns3
> https://patches.dpdk.org/project/dpdk/list/?series=24533
>
> Chengwen Feng (5):
> net/hns3: fix header file self contained
> net/hns3: remove unused structure definition
> net/hns3: do not use reserved identifier macro
> net/hns3: revert fix mailbox communication with HW
> net/hns3: fix VF mark wrong message processed
>
> Dongdong Liu (1):
> net/hns3: fix gcov compile warning
>
> Huisong Li (11):
> net/hns3: fix have no valid RSS rule
> net/hns3: fix RSS filter restore
> net/hns3: fix the lock protection of RSS flow rule
> net/hns3: fix RSS flow rule restore failed
> net/hns3: move flow direction rule recovery position
> net/hns3: fix hns3 restore filter function input
> net/hns3: fix incorrect packet type report for GENEVE
> net/hns3: fix fail to enable IPV4 or IPV6 packet RSS
> net/hns3: fix some spelling errors
> net/hns3: fix inconsistent RSS behavior
> net/hns3: add check for L3 and L4 type
>
> Jie Hai (2):
> net/hns3: fix magic numbers
> net/hns3: fix the obtaination of minimum Tx frame length
>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2022-10-05 6:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 7:22 Dongdong Liu
2022-09-30 7:22 ` [PATCH 01/19] net/hns3: fix have no valid RSS rule Dongdong Liu
2022-09-30 7:22 ` [PATCH 02/19] net/hns3: fix RSS filter restore Dongdong Liu
2022-09-30 7:22 ` [PATCH 03/19] net/hns3: fix the lock protection of RSS flow rule Dongdong Liu
2022-09-30 7:22 ` [PATCH 04/19] net/hns3: fix RSS flow rule restore failed Dongdong Liu
2022-09-30 7:22 ` [PATCH 05/19] net/hns3: move flow direction rule recovery position Dongdong Liu
2022-09-30 7:22 ` [PATCH 06/19] net/hns3: fix hns3 restore filter function input Dongdong Liu
2022-09-30 7:22 ` [PATCH 07/19] net/hns3: fix gcov compile warning Dongdong Liu
2022-09-30 7:22 ` [PATCH 08/19] net/hns3: fix incorrect packet type report for GENEVE Dongdong Liu
2022-09-30 7:22 ` [PATCH 09/19] net/hns3: fix magic numbers Dongdong Liu
2022-09-30 7:22 ` [PATCH 10/19] net/hns3: fix header file self contained Dongdong Liu
2022-09-30 7:22 ` [PATCH 11/19] net/hns3: remove unused structure definition Dongdong Liu
2022-09-30 7:22 ` [PATCH 12/19] net/hns3: do not use reserved identifier macro Dongdong Liu
2022-09-30 7:22 ` [PATCH 13/19] net/hns3: fix fail to enable IPV4 or IPV6 packet RSS Dongdong Liu
2022-09-30 7:22 ` [PATCH 14/19] net/hns3: fix some spelling errors Dongdong Liu
2022-09-30 7:22 ` [PATCH 15/19] net/hns3: fix inconsistent RSS behavior Dongdong Liu
2022-09-30 7:22 ` [PATCH 16/19] net/hns3: add check for L3 and L4 type Dongdong Liu
2022-09-30 7:22 ` [PATCH 17/19] net/hns3: revert fix mailbox communication with HW Dongdong Liu
2022-09-30 7:22 ` [PATCH 18/19] net/hns3: fix VF mark wrong message processed Dongdong Liu
2022-09-30 7:22 ` [PATCH 19/19] net/hns3: fix the obtaination of minimum Tx frame length Dongdong Liu
2022-10-05 6:18 ` Andrew Rybchenko [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=41f31c7b-1139-3519-dbea-5bf66019b5c3@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=ferruh.yigit@amd.com \
--cc=haijie1@huawei.com \
--cc=lihuisong@huawei.com \
--cc=liudongdong3@huawei.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=yisen.zhuang@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).