From: Davide Caratti <dcaratti@redhat.com>
To: mptcp@lists.linux.dev
Subject: [PATCH mptcp-next v4 0/6] mptcp: convert netlink code to use YAML spec
Date: Wed, 20 Sep 2023 11:24:43 +0200 [thread overview]
Message-ID: <cover.1695201346.git.dcaratti@redhat.com> (raw)
this series converts most of the MPTCP netlink interface (plus uAPI bits)
to use sources generated by a YAML spec file. Patch 2/6 and 6/6 have been
individually verified with kselftests.
POC:
$ sudo ./tools/net/ynl/cli.py --spec \
> Documentation/netlink/specs/mptcp.yaml --do add_addr \
> --json '{"addr": {"addr4": 16909061, "family": 2, "flags": 4, "id": 10, "port": 0}}'
$ ip -j mptcp endpoint show id 10
[{"address":"1.2.3.5","id":10,"backup":true}]
v4:
- removed unwanted whitespaces, update MAINTAINERS (Matthieu Baerts)
v3:
- add missing 'static' keyword (MPTCP CI)
- fix element ordering for 'attr' attributes in patch 2,
mptcp spec and generated C code (Paolo Abeni)
- removed extra newline, deuglified subjects in patch 2 and 4
v2:
- mptcp.yaml: only put values around enum "holes" (Paolo Abeni)
- _doit and _dumpit renames are done in a dedicate patch (Paolo Abeni)
- removed useless nla_policy passed through parse_entry() (Paolo Abeni)
- renamed mptcp_pm_address_nl_policy in patch 2 (Paolo Abeni)
- (hopefully) more comprehensible commit messages (Paolo Abeni)
Davide Caratti (6):
tools: ynl: add uns-admin-perm to genetlink legacy
net: mptcp: convert netlink from small_ops to ops
Documentation: netlink: add a YAML spec for mptcp
uapi: mptcp: use header file generated from YAML spec
net: mptcp: rename netlink handlers to
mptcp_pm_nl_<blah>_{doit,dumpit}
net: mptcp: use policy generated by YAML spec
Documentation/netlink/genetlink-legacy.yaml | 2 +-
Documentation/netlink/specs/mptcp.yaml | 394 ++++++++++++++++++++
MAINTAINERS | 3 +-
include/uapi/linux/mptcp.h | 174 +--------
include/uapi/linux/mptcp_pm.h | 149 ++++++++
net/mptcp/Makefile | 3 +-
net/mptcp/mptcp_pm_gen.c | 179 +++++++++
net/mptcp/mptcp_pm_gen.h | 58 +++
net/mptcp/pm_netlink.c | 114 +-----
net/mptcp/pm_userspace.c | 8 +-
net/mptcp/protocol.h | 6 +-
11 files changed, 816 insertions(+), 274 deletions(-)
create mode 100644 Documentation/netlink/specs/mptcp.yaml
create mode 100644 include/uapi/linux/mptcp_pm.h
create mode 100644 net/mptcp/mptcp_pm_gen.c
create mode 100644 net/mptcp/mptcp_pm_gen.h
--
2.41.0
next reply other threads:[~2023-09-20 9:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 9:24 Davide Caratti [this message]
2023-09-20 9:24 ` [PATCH mptcp-next v4 1/6] tools: ynl: add uns-admin-perm to genetlink legacy Davide Caratti
2023-09-20 9:24 ` [PATCH mptcp-next v4 2/6] net: mptcp: convert netlink from small_ops to ops Davide Caratti
2023-09-20 9:24 ` [PATCH mptcp-next v4 3/6] Documentation: netlink: add a YAML spec for mptcp Davide Caratti
2023-09-20 9:24 ` [PATCH mptcp-next v4 4/6] uapi: mptcp: use header file generated from YAML spec Davide Caratti
2023-09-20 9:24 ` [PATCH mptcp-next v4 5/6] net: mptcp: rename netlink handlers to mptcp_pm_nl_<blah>_{doit,dumpit} Davide Caratti
2023-09-20 9:24 ` [PATCH mptcp-next v4 6/6] net: mptcp: use policy generated by YAML spec Davide Caratti
2023-09-20 10:30 ` net: mptcp: use policy generated by YAML spec: Tests Results MPTCP CI
2023-09-23 7:55 ` [PATCH mptcp-next v4 0/6] mptcp: convert netlink code to use YAML spec Matthieu Baerts
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=cover.1695201346.git.dcaratti@redhat.com \
--to=dcaratti@redhat.com \
--cc=mptcp@lists.linux.dev \
/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.