From: Davide Caratti <dcaratti@redhat.com>
To: mptcp@lists.linux.dev
Subject: [PATCH mptcp-next 0/5] v2 fixes for "mptcp: convert Netlink code to use YAML spec"
Date: Mon, 16 Oct 2023 15:43:06 +0200 [thread overview]
Message-ID: <cover.1697463031.git.dcaratti@redhat.com> (raw)
v2 changes:
- de-uglify YAML spef file, replacing '_' with '-' and avoiding
unnecessary assignments in enums (Jakub Kicinski)
- keep validating addr6 with NLA_POLICY_EXACT_LEN() (Jakub Kicinski)
- Don't leave MPTCP_EVENT_UNSPEC undocumented (Simon Horman)
patch 1/5 will cause a small context mismatch in "net: mptcp: use policy
generated by YAML spec"
Davide Caratti (5):
Squash-to: "net: mptcp: convert netlink from small_ops to ops"
Squash-to: "Documentation: netlink: add a YAML spec for mptcp"
Squash-to: "uapi: mptcp: use header file generated from YAML spec"
Squash to: "net: mptcp: use policy generated by YAML spec"
tools: ynl-gen: add support for exact-len validation
--
2.41.0
next reply other threads:[~2023-10-16 13:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 13:43 Davide Caratti [this message]
2023-10-16 13:43 ` [PATCH mptcp-next 1/5] Squash-to: "net: mptcp: convert netlink from small_ops to ops" Davide Caratti
2023-10-16 13:43 ` [PATCH mptcp-next 2/5] Squash-to: "Documentation: netlink: add a YAML spec for mptcp" Davide Caratti
2023-10-16 13:43 ` [PATCH mptcp-next 3/5] Squash-to: "uapi: mptcp: use header file generated from YAML spec" Davide Caratti
2023-10-16 13:43 ` [PATCH mptcp-next 4/5] Squash to: "net: mptcp: use policy generated by " Davide Caratti
2023-10-16 13:43 ` [PATCH mptcp-next 5/5] tools: ynl-gen: add support for exact-len validation Davide Caratti
2023-10-16 20:40 ` tools: ynl-gen: add support for exact-len validation: Tests Results MPTCP CI
2023-10-16 21:45 ` MPTCP CI
2023-10-19 10:48 ` [PATCH mptcp-next 0/5] v2 fixes for "mptcp: convert Netlink code to use YAML spec" Matthieu Baerts
2023-10-19 11:08 ` Davide Caratti
2023-10-21 13:47 ` 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.1697463031.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.