From: patchwork-bot+netdevbpf@kernel.org
To: Guangbin Huang <huangguangbin2@huawei.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, lipeng321@huawei.com
Subject: Re: [PATCH net-next 0/7] net: hns3: updates for -next
Date: Sat, 28 Aug 2021 11:30:07 +0000 [thread overview]
Message-ID: <163015020762.6002.7204106144886247674.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1630133721-9260-1-git-send-email-huangguangbin2@huawei.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Sat, 28 Aug 2021 14:55:14 +0800 you wrote:
> This series includes some updates for the HNS3 ethernet driver.
>
> #1 add a trace in hclge_gen_resp_to_vf().
> #2~#4 refactor some functions.
> #5~#7 add some cleanups.
>
> This series includes some optimizations, cleanups and one
>
> [...]
Here is the summary with links:
- [net-next,1/7] net: hns3: add trace event in hclge_gen_resp_to_vf()
https://git.kernel.org/netdev/net-next/c/0fc36e37d5c0
- [net-next,2/7] net: hns3: refactor function hclge_parse_capability()
https://git.kernel.org/netdev/net-next/c/e1d93bc6ef3b
- [net-next,3/7] net: hns3: refactor function hclgevf_parse_capability()
https://git.kernel.org/netdev/net-next/c/81414ba71356
- [net-next,4/7] net: hns3: add new function hclge_get_speed_bit()
https://git.kernel.org/netdev/net-next/c/aec35aecc3cc
- [net-next,5/7] net: hns3: don't config TM DWRR twice when set ETS
https://git.kernel.org/netdev/net-next/c/7f2f8cf6ef66
- [net-next,6/7] net: hns3: remove unnecessary "static" of local variables in function
https://git.kernel.org/netdev/net-next/c/1026b1534fa1
- [net-next,7/7] net: hns3: add required space in comment
https://git.kernel.org/netdev/net-next/c/0cb0704149f0
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-08-28 11:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-28 6:55 [PATCH net-next 0/7] net: hns3: updates for -next Guangbin Huang
2021-08-28 6:55 ` [PATCH net-next 1/7] net: hns3: add trace event in hclge_gen_resp_to_vf() Guangbin Huang
2021-08-28 6:55 ` [PATCH net-next 2/7] net: hns3: refactor function hclge_parse_capability() Guangbin Huang
2021-08-28 6:55 ` [PATCH net-next 3/7] net: hns3: refactor function hclgevf_parse_capability() Guangbin Huang
2021-08-28 6:55 ` [PATCH net-next 4/7] net: hns3: add new function hclge_get_speed_bit() Guangbin Huang
2021-08-28 6:55 ` [PATCH net-next 5/7] net: hns3: don't config TM DWRR twice when set ETS Guangbin Huang
2021-08-28 6:55 ` [PATCH net-next 6/7] net: hns3: remove unnecessary "static" of local variables in function Guangbin Huang
2021-08-28 6:55 ` [PATCH net-next 7/7] net: hns3: add required space in comment Guangbin Huang
2021-08-28 11:30 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-16 6:36 [PATCH net-next 0/7] net: hns3: updates for -next Guangbin Huang
2020-12-10 3:42 Huazhong Tan
2020-12-10 4:34 ` David Miller
2020-11-27 8:47 Huazhong Tan
2020-09-29 9:31 Huazhong Tan
2020-09-29 18:02 ` Jakub Kicinski
2020-09-29 20:14 ` David Miller
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=163015020762.6002.7204106144886247674.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=huangguangbin2@huawei.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lipeng321@huawei.com \
--cc=netdev@vger.kernel.org \
/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).