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
Subject: Re: [PATCH V2 net-next 00/13] net: hns3: some cleanups for -next
Date: Fri, 12 Feb 2021 21:20:10 +0000 [thread overview]
Message-ID: <161316481044.12385.10525514068157683118.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210212032113.5384-1-tanhuazhong@huawei.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Fri, 12 Feb 2021 11:21:00 +0800 you wrote:
> To improve code readability and maintainability, the series
> refactor out some bloated functions in the HNS3 ethernet driver.
>
> change log:
> V2: remove an unused variable in #5
>
> previous version:
> V1: https://patchwork.kernel.org/project/netdevbpf/cover/1612943005-59416-1-git-send-email-tanhuazhong@huawei.com/
>
> [...]
Here is the summary with links:
- [V2,net-next,01/13] net: hns3: refactor out hclge_cmd_convert_err_code()
https://git.kernel.org/netdev/net-next/c/1c9a98b0ba1f
- [V2,net-next,02/13] net: hns3: refactor out hclgevf_cmd_convert_err_code()
https://git.kernel.org/netdev/net-next/c/433e2802775c
- [V2,net-next,03/13] net: hns3: clean up hns3_dbg_cmd_write()
https://git.kernel.org/netdev/net-next/c/c318af3f5684
- [V2,net-next,04/13] net: hns3: use ipv6_addr_any() helper
https://git.kernel.org/netdev/net-next/c/eaede835675c
- [V2,net-next,05/13] net: hns3: refactor out hclge_set_vf_vlan_common()
https://git.kernel.org/netdev/net-next/c/88936e320c1a
- [V2,net-next,06/13] net: hns3: refactor out hclge_get_rss_tuple()
https://git.kernel.org/netdev/net-next/c/405642a15cba
- [V2,net-next,07/13] net: hns3: refactor out hclgevf_get_rss_tuple()
https://git.kernel.org/netdev/net-next/c/73f7767ed0f9
- [V2,net-next,08/13] net: hns3: split out hclge_dbg_dump_qos_buf_cfg()
https://git.kernel.org/netdev/net-next/c/b3712fa73d56
- [V2,net-next,09/13] net: hns3: split out hclge_cmd_send()
https://git.kernel.org/netdev/net-next/c/76f82fd9b123
- [V2,net-next,10/13] net: hns3: split out hclgevf_cmd_send()
https://git.kernel.org/netdev/net-next/c/eb0faf32b86e
- [V2,net-next,11/13] net: hns3: refactor out hclge_set_rss_tuple()
https://git.kernel.org/netdev/net-next/c/e291eff3bce4
- [V2,net-next,12/13] net: hns3: refactor out hclgevf_set_rss_tuple()
https://git.kernel.org/netdev/net-next/c/5fd0e7b4f7bf
- [V2,net-next,13/13] net: hns3: refactor out hclge_rm_vport_all_mac_table()
https://git.kernel.org/netdev/net-next/c/80a9f3f1fa81
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-02-12 21:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 3:21 [PATCH V2 net-next 00/13] net: hns3: some cleanups for -next Huazhong Tan
2021-02-12 3:21 ` [PATCH V2 net-next 01/13] net: hns3: refactor out hclge_cmd_convert_err_code() Huazhong Tan
2021-02-12 3:21 ` [PATCH V2 net-next 02/13] net: hns3: refactor out hclgevf_cmd_convert_err_code() Huazhong Tan
2021-02-12 3:21 ` [PATCH V2 net-next 03/13] net: hns3: clean up hns3_dbg_cmd_write() Huazhong Tan
2021-02-12 3:21 ` [PATCH V2 net-next 04/13] net: hns3: use ipv6_addr_any() helper Huazhong Tan
2021-02-12 3:21 ` [PATCH V2 net-next 05/13] net: hns3: refactor out hclge_set_vf_vlan_common() Huazhong Tan
2021-02-12 3:21 ` [PATCH V2 net-next 06/13] net: hns3: refactor out hclge_get_rss_tuple() Huazhong Tan
2021-02-12 3:21 ` [PATCH V2 net-next 07/13] net: hns3: refactor out hclgevf_get_rss_tuple() Huazhong Tan
2021-02-12 3:21 ` [PATCH V2 net-next 08/13] net: hns3: split out hclge_dbg_dump_qos_buf_cfg() Huazhong Tan
2021-02-12 21:20 ` 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=161316481044.12385.10525514068157683118.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@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).