From: patchwork-bot+netdevbpf@kernel•org
To: Hangbin Liu <liuhangbin@gmail•com>
Cc: netdev@vger•kernel.org, davem@davemloft•net, edumazet@google•com,
kuba@kernel•org, pabeni@redhat•com, donald.hunter@gmail•com,
jiri@resnulli•us, jacob.e.keller@intel•com, sdf@google•com
Subject: Re: [PATCHv4 net-next 0/4] doc/netlink: add a YAML spec for team
Date: Wed, 03 Apr 2024 01:40:34 +0000 [thread overview]
Message-ID: <171210843471.14193.9758845608853454018.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240401031004.1159713-1-liuhangbin@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel•org>:
On Mon, 1 Apr 2024 11:10:00 +0800 you wrote:
> Add a YAML spec for team. As we need to link two objects together to form
> the team module, rename team to team_core for linking.
>
> v4:
> 1. fix the wrong squashe changes (Jakub Kicinski)
> v3:
> 1. remove item/list-option from request as they are not attributes (Jakub Kicinski)
> v2:
> 1. adjust the continuation line (Jakub Kicinski)
> 2. adjust the family maxattr (Jakub Kicinski)
> v1:
> 1. remove dump from team options. (Jiri Pirko)
>
> [...]
Here is the summary with links:
- [PATCHv4,net-next,1/4] Documentation: netlink: add a YAML spec for team
https://git.kernel.org/netdev/net-next/c/387724cbf415
- [PATCHv4,net-next,2/4] net: team: rename team to team_core for linking
https://git.kernel.org/netdev/net-next/c/a0393e3e3ddb
- [PATCHv4,net-next,3/4] net: team: use policy generated by YAML spec
https://git.kernel.org/netdev/net-next/c/948dbafc15da
- [PATCHv4,net-next,4/4] uapi: team: use header file generated from YAML spec
https://git.kernel.org/netdev/net-next/c/e57ba7e3d7bc
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:[~2024-04-03 1:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 3:10 [PATCHv4 net-next 0/4] doc/netlink: add a YAML spec for team Hangbin Liu
2024-04-01 3:10 ` [PATCHv4 net-next 1/4] Documentation: netlink: " Hangbin Liu
2024-04-02 12:22 ` Jiri Pirko
2024-04-02 14:45 ` Jakub Kicinski
2024-04-01 3:10 ` [PATCHv4 net-next 2/4] net: team: rename team to team_core for linking Hangbin Liu
2024-04-02 12:23 ` [PATCH net v1] dpll: indent DPLL option type by a tab Jiri Pirko
2024-04-01 3:10 ` [PATCHv4 net-next 3/4] net: team: use policy generated by YAML spec Hangbin Liu
2024-04-02 12:23 ` Jiri Pirko
2024-04-01 3:10 ` [PATCHv4 net-next 4/4] uapi: team: use header file generated from " Hangbin Liu
2024-04-02 12:24 ` Jiri Pirko
2024-04-03 1:40 ` 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=171210843471.14193.9758845608853454018.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=donald.hunter@gmail$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=jacob.e.keller@intel$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=kuba@kernel$(echo .)org \
--cc=liuhangbin@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=sdf@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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