From: Hangbin Liu <liuhangbin@gmail.com>
To: netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Donald Hunter <donald.hunter@gmail.com>,
Jiri Pirko <jiri@resnulli.us>,
Jacob Keller <jacob.e.keller@intel.com>,
Stanislav Fomichev <sdf@google.com>,
Hangbin Liu <liuhangbin@gmail.com>
Subject: [PATCHv4 net-next 0/4] doc/netlink: add a YAML spec for team
Date: Mon, 1 Apr 2024 11:10:00 +0800 [thread overview]
Message-ID: <20240401031004.1159713-1-liuhangbin@gmail.com> (raw)
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)
Hangbin Liu (4):
Documentation: netlink: add a YAML spec for team
net: team: rename team to team_core for linking
net: team: use policy generated by YAML spec
uapi: team: use header file generated from YAML spec
Documentation/netlink/specs/team.yaml | 204 +++++++++++++++++++++++
MAINTAINERS | 1 +
drivers/net/team/Makefile | 1 +
drivers/net/team/{team.c => team_core.c} | 63 +------
drivers/net/team/team_nl.c | 59 +++++++
drivers/net/team/team_nl.h | 29 ++++
include/uapi/linux/if_team.h | 116 +++++--------
7 files changed, 346 insertions(+), 127 deletions(-)
create mode 100644 Documentation/netlink/specs/team.yaml
rename drivers/net/team/{team.c => team_core.c} (97%)
create mode 100644 drivers/net/team/team_nl.c
create mode 100644 drivers/net/team/team_nl.h
--
2.43.0
next reply other threads:[~2024-04-01 3:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 3:10 Hangbin Liu [this message]
2024-04-01 3:10 ` [PATCHv4 net-next 1/4] Documentation: netlink: add a YAML spec for team 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 ` [PATCHv4 net-next 0/4] doc/netlink: add a YAML spec for team patchwork-bot+netdevbpf
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=20240401031004.1159713-1-liuhangbin@gmail.com \
--to=liuhangbin@gmail.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=jacob.e.keller@intel.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@google.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).