From: patchwork-bot+netdevbpf@kernel.org
To: Zhengchao Shao <shaozhengchao@huawei.com>
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
jiri@resnulli.us, weiyongjun1@huawei.com, yuehaibing@huawei.com
Subject: Re: [PATCH net-next,v3 0/5] team: do some cleanups in team driver
Date: Tue, 08 Aug 2023 22:10:26 +0000 [thread overview]
Message-ID: <169153262638.13746.11740842045529374068.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230807012556.3146071-1-shaozhengchao@huawei.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 7 Aug 2023 09:25:51 +0800 you wrote:
> Do some cleanups in team driver.
>
> ---
> v3: add header file back to team_mode_activebackup.c
> v2: combine patch 5/6 and patch 6/6 into patch 5/5
> ---
> Zhengchao Shao (5):
> team: add __exit modifier to team_nl_fini()
> team: remove unreferenced header in broadcast and roundrobin files
> team: change the init function in the team_option structure to void
> team: change the getter function in the team_option structure to void
> team: remove unused input parameters in lb_htpm_select_tx_port and
> lb_hash_select_tx_port
>
> [...]
Here is the summary with links:
- [net-next,v3,1/5] team: add __exit modifier to team_nl_fini()
https://git.kernel.org/netdev/net-next/c/8958ef511a01
- [net-next,v3,2/5] team: remove unreferenced header in broadcast and roundrobin files
https://git.kernel.org/netdev/net-next/c/adac119421c3
- [net-next,v3,3/5] team: change the init function in the team_option structure to void
https://git.kernel.org/netdev/net-next/c/de3ecc4fd8bf
- [net-next,v3,4/5] team: change the getter function in the team_option structure to void
https://git.kernel.org/netdev/net-next/c/c3b41f4c7b7c
- [net-next,v3,5/5] team: remove unused input parameters in lb_htpm_select_tx_port and lb_hash_select_tx_port
https://git.kernel.org/netdev/net-next/c/7790eaeb688f
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:[~2023-08-08 22:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 1:25 [PATCH net-next,v3 0/5] team: do some cleanups in team driver Zhengchao Shao
2023-08-07 1:25 ` [PATCH net-next,v3 1/5] team: add __exit modifier to team_nl_fini() Zhengchao Shao
2023-08-07 1:25 ` [PATCH net-next,v3 2/5] team: remove unreferenced header in broadcast and roundrobin files Zhengchao Shao
2023-08-07 1:25 ` [PATCH net-next,v3 3/5] team: change the init function in the team_option structure to void Zhengchao Shao
2023-08-07 1:25 ` [PATCH net-next,v3 4/5] team: change the getter " Zhengchao Shao
2023-08-07 1:25 ` [PATCH net-next,v3 5/5] team: remove unused input parameters in lb_htpm_select_tx_port and lb_hash_select_tx_port Zhengchao Shao
2023-08-07 2:54 ` [PATCH net-next,v3 0/5] team: do some cleanups in team driver Hangbin Liu
2023-08-07 7:46 ` Jiri Pirko
2023-08-08 22: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=169153262638.13746.11740842045529374068.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shaozhengchao@huawei.com \
--cc=weiyongjun1@huawei.com \
--cc=yuehaibing@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.