From: Donald Hunter <donald.hunter@gmail.com>
To: netdev@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Cc: donald.hunter@redhat.com, Donald Hunter <donald.hunter@gmail.com>
Subject: [PATCH net-next v5 0/7] ynl: add support for user headers and struct attrs
Date: Mon, 27 Mar 2023 09:31:31 +0100 [thread overview]
Message-ID: <20230327083138.96044-1-donald.hunter@gmail.com> (raw)
Add support for user headers and struct attrs to YNL. This patchset adds
features to ynl and add a partial spec for openvswitch that demonstrates
use of the features.
Patch 1-4 add features to ynl
Patch 5 adds partial openvswitch specs that demonstrate the new features
Patch 6-7 add documentation for legacy structs and for sub-type
v4 - v5: all requested by Jakub Kicinski
- Describe C struct packing sematics in docs
- Rework struct example
- Change sub-type doc to use text from Jakub
- Add struct_name and sub_type as fields of class SpecAttr
- Fix typos and wrap at 80 chars
- Clean up signature formatting in python code
v3 - v4:
- Rebase to net-next after net-6.3-rc4 merge
v2 - v3: all requested by Jakub Kicinski
- Drop genlmsg fix that was applied separately
- Don't mention 'kernel' types, leave it to schema
- Avoid passing fixed header around in python code
- Use 'binary' with 'sub-type' for C arrays
- Use 'binary' with 'struct' for C structs
- Add docs for structs and sub-type
v1 - v2: all requested by Jakub Kicinski
- Split ynl changes into separate patches
- Rename user-header to fixed-header and improve description
- Move fixed-header to operations section of spec
- Introduce objects to represent struct config in nlspec
- Use kebab-case throughout openvswitch specs
Donald Hunter (7):
tools: ynl: Add struct parsing to nlspec
tools: ynl: Add C array attribute decoding to ynl
tools: ynl: Add struct attr decoding to ynl
tools: ynl: Add fixed-header support to ynl
netlink: specs: add partial specification for openvswitch
docs: netlink: document struct support for genetlink-legacy
docs: netlink: document the sub-type attribute property
Documentation/netlink/genetlink-legacy.yaml | 16 ++
Documentation/netlink/specs/ovs_datapath.yaml | 153 ++++++++++++++++++
Documentation/netlink/specs/ovs_vport.yaml | 139 ++++++++++++++++
.../netlink/genetlink-legacy.rst | 88 +++++++++-
Documentation/userspace-api/netlink/specs.rst | 10 ++
tools/net/ynl/lib/nlspec.py | 73 +++++++--
tools/net/ynl/lib/ynl.py | 55 ++++++-
7 files changed, 516 insertions(+), 18 deletions(-)
create mode 100644 Documentation/netlink/specs/ovs_datapath.yaml
create mode 100644 Documentation/netlink/specs/ovs_vport.yaml
--
2.39.0
next reply other threads:[~2023-03-27 8:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 8:31 Donald Hunter [this message]
2023-03-27 8:31 ` [PATCH net-next v5 1/7] tools: ynl: Add struct parsing to nlspec Donald Hunter
2023-03-27 8:31 ` [PATCH net-next v5 2/7] tools: ynl: Add C array attribute decoding to ynl Donald Hunter
2023-03-27 8:31 ` [PATCH net-next v5 3/7] tools: ynl: Add struct attr " Donald Hunter
2023-03-27 8:31 ` [PATCH net-next v5 4/7] tools: ynl: Add fixed-header support " Donald Hunter
2023-03-27 8:31 ` [PATCH net-next v5 5/7] netlink: specs: add partial specification for openvswitch Donald Hunter
2023-03-27 8:31 ` [PATCH net-next v5 6/7] docs: netlink: document struct support for genetlink-legacy Donald Hunter
2023-03-27 12:44 ` Bagas Sanjaya
2023-03-27 14:39 ` Akira Yokosawa
2023-03-28 8:38 ` Bagas Sanjaya
2023-03-27 8:31 ` [PATCH net-next v5 7/7] docs: netlink: document the sub-type attribute property Donald Hunter
2023-03-27 12:45 ` Bagas Sanjaya
2023-03-29 7:00 ` [PATCH net-next v5 0/7] ynl: add support for user headers and struct attrs 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=20230327083138.96044-1-donald.hunter@gmail.com \
--to=donald.hunter@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=donald.hunter@redhat.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--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).