[PATCH net-next 0/6] mptcp: convert Netlink code to use YAML spec

[Matthieu Baerts]

This series from Davide converts most of the MPTCP Netlink interface
(plus uAPI bits) to use sources generated by YNL using a YAML spec file.

This new YAML file is useful to validate the API and to generate a good
documentation page.

Patch 1 modifies YNL spec to support "uns-admin-perm" for genetlink
legacy.

Patch 2 converts Netlink structures from small_ops to ops to prepare the
switch to YAML.

Patch 3 adds the Netlink YAML spec for MPTCP.

Patch 4 adds and uses a new header file generated from the new YAML
spec.

Patch 5 renames some handlers to match the ones generated from the YAML
spec.

Patch 6 adds and uses Netlink policies automatically generated from the
YAML spec.

Signed-off-by: Matthieu Baerts <matttbe@xxxxxxxxxx>
---
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(-)
---
base-commit: f0107b864f004bc6fa19bf6d5074b4a366f3e16a
change-id: 20231006-upstream-net-next-20231006-mptcp-ynl-0d3c99b1ed79

Best regards,
-- 
Matthieu Baerts <matttbe@xxxxxxxxxx>