From: patchwork-bot+netdevbpf@kernel.org
To: Huazhong Tan <tanhuazhong@huawei.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
salil.mehta@huawei.com, yisen.zhuang@huawei.com,
huangdaode@huawei.com, linuxarm@openeuler.org,
linuxarm@huawei.com
Subject: Re: [PATCH V2 net-next 0/7] net: hns3: refactor and new features for flow director
Date: Mon, 22 Mar 2021 20:10:10 +0000 [thread overview]
Message-ID: <161644381036.22637.12567078527418286788.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1616385122-48198-1-git-send-email-tanhuazhong@huawei.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Mon, 22 Mar 2021 11:51:55 +0800 you wrote:
> This patchset refactor some functions and add some new features for
> flow director.
>
> patch 1~3: refactor large functions
> patch 4, 7: add traffic class and user-def field support for ethtool
> patch 5: refactor flow director configuration
> patch 6: clean up for hns3_del_all_fd_entries()
>
> [...]
Here is the summary with links:
- [V2,net-next,1/7] net: hns3: refactor out hclge_add_fd_entry()
https://git.kernel.org/netdev/net-next/c/5f2b1238b33c
- [V2,net-next,2/7] net: hns3: refactor out hclge_fd_get_tuple()
https://git.kernel.org/netdev/net-next/c/74b755d1dbf1
- [V2,net-next,3/7] net: hns3: refactor for function hclge_fd_convert_tuple
https://git.kernel.org/netdev/net-next/c/fb72699dfef8
- [V2,net-next,4/7] net: hns3: add support for traffic class tuple support for flow director by ethtool
https://git.kernel.org/netdev/net-next/c/ae4811913f57
- [V2,net-next,5/7] net: hns3: refactor flow director configuration
https://git.kernel.org/netdev/net-next/c/fc4243b8de8b
- [V2,net-next,6/7] net: hns3: refine for hns3_del_all_fd_entries()
https://git.kernel.org/netdev/net-next/c/f07203b0180f
- [V2,net-next,7/7] net: hns3: add support for user-def data of flow director
https://git.kernel.org/netdev/net-next/c/67b0e1428e2f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-03-22 20:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 3:51 [PATCH V2 net-next 0/7] net: hns3: refactor and new features for flow director Huazhong Tan
2021-03-22 3:51 ` [PATCH V2 net-next 1/7] net: hns3: refactor out hclge_add_fd_entry() Huazhong Tan
2021-03-22 3:51 ` [PATCH V2 net-next 2/7] net: hns3: refactor out hclge_fd_get_tuple() Huazhong Tan
2021-03-22 3:51 ` [PATCH V2 net-next 3/7] net: hns3: refactor for function hclge_fd_convert_tuple Huazhong Tan
2021-03-22 3:51 ` [PATCH V2 net-next 4/7] net: hns3: add support for traffic class tuple support for flow director by ethtool Huazhong Tan
2021-03-22 3:52 ` [PATCH V2 net-next 5/7] net: hns3: refactor flow director configuration Huazhong Tan
2021-03-22 3:52 ` [PATCH V2 net-next 6/7] net: hns3: refine for hns3_del_all_fd_entries() Huazhong Tan
2021-03-22 3:52 ` [PATCH V2 net-next 7/7] net: hns3: add support for user-def data of flow director Huazhong Tan
2021-03-22 20:10 ` patchwork-bot+netdevbpf [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=161644381036.22637.12567078527418286788.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=huangdaode@huawei.com \
--cc=kuba@kernel.org \
--cc=linuxarm@huawei.com \
--cc=linuxarm@openeuler.org \
--cc=netdev@vger.kernel.org \
--cc=salil.mehta@huawei.com \
--cc=tanhuazhong@huawei.com \
--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).