From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
donald.hunter@gmail.com, Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net-next 0/3] netlink: specs: prep legacy specs for C code gen
Date: Wed, 13 Dec 2023 15:28:19 -0800 [thread overview]
Message-ID: <20231213232822.2950853-1-kuba@kernel.org> (raw)
Minor adjustments to some specs to make them ready for C code gen.
Jakub Kicinski (3):
netlink: specs: ovs: remove fixed header fields from attrs
netlink: specs: ovs: correct enum names in specs
netlink: specs: mptcp: rename the MPTCP path management(?) spec
Documentation/netlink/specs/{mptcp.yaml => mptcp_pm.yaml} | 0
Documentation/netlink/specs/ovs_datapath.yaml | 3 +--
Documentation/netlink/specs/ovs_flow.yaml | 7 ++++---
Documentation/netlink/specs/ovs_vport.yaml | 4 ----
include/uapi/linux/mptcp_pm.h | 2 +-
net/mptcp/mptcp_pm_gen.c | 2 +-
net/mptcp/mptcp_pm_gen.h | 2 +-
7 files changed, 8 insertions(+), 12 deletions(-)
rename Documentation/netlink/specs/{mptcp.yaml => mptcp_pm.yaml} (100%)
--
2.43.0
next reply other threads:[~2023-12-13 23:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 23:28 Jakub Kicinski [this message]
2023-12-13 23:28 ` [PATCH net-next 1/3] netlink: specs: ovs: remove fixed header fields from attrs Jakub Kicinski
2023-12-14 8:40 ` Donald Hunter
2023-12-13 23:28 ` [PATCH net-next 2/3] netlink: specs: ovs: correct enum names in specs Jakub Kicinski
2023-12-14 8:45 ` Donald Hunter
2023-12-13 23:28 ` [PATCH net-next 3/3] netlink: specs: mptcp: rename the MPTCP path management(?) spec Jakub Kicinski
2023-12-13 23:38 ` Mat Martineau
2023-12-14 8:42 ` Donald Hunter
2023-12-14 17:24 ` kernel test robot
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=20231213232822.2950853-1-kuba@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).