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>,
Jacob Keller <jacob.e.keller@intel.com>,
Jiri Pirko <jiri@resnulli.us>,
Stanislav Fomichev <sdf@google.com>
Cc: donald.hunter@redhat.com, Donald Hunter <donald.hunter@gmail.com>
Subject: [PATCH net-next v3 0/6] tools/net/ynl: Add support for nlctrl netlink family
Date: Wed, 6 Mar 2024 23:10:40 +0000 [thread overview]
Message-ID: <20240306231046.97158-1-donald.hunter@gmail.com> (raw)
This series adds a new YNL spec for the nlctrl family, plus some fixes
and enhancements for ynl.
Patch 1 fixes an extack decoding bug
Patch 2 gives cleaner netlink error reporting
Patch 3 fixes an array-nest codegen bug
Patch 4 adds nest-type-value support to ynl
Patch 5 fixes the ynl schemas to allow empty enum-name attrs
Patch 6 contains the nlctrl spec
Changes from v2 -> v3:
- Add a better description to the nlctrl spec (Jakub)
- Format all codegen names using lower-kebab-case (Jakub)
- Add a patch to fix the schemas
Changes from v1 -> v2:
- Added patch 3 to fix codegen bug
- Removed multi-level array-nest patch
- Added nest-type-value patch
- Updated nlctrl spec to align with headers and fix compilation
Donald Hunter (6):
tools/net/ynl: Fix extack decoding for netlink-raw
tools/net/ynl: Report netlink errors without stacktrace
tools/net/ynl: Fix c codegen for array-nest
tools/net/ynl: Add nest-type-value decoding
doc/netlink: Allow empty enum-name in ynl specs
doc/netlink/specs: Add spec for nlctrl netlink family
Documentation/netlink/genetlink-c.yaml | 15 +-
Documentation/netlink/genetlink-legacy.yaml | 15 +-
Documentation/netlink/netlink-raw.yaml | 15 +-
Documentation/netlink/specs/nlctrl.yaml | 207 ++++++++++++++++++++
tools/net/ynl/cli.py | 18 +-
tools/net/ynl/lib/__init__.py | 4 +-
tools/net/ynl/lib/ynl.py | 19 +-
tools/net/ynl/ynl-gen-c.py | 2 +-
8 files changed, 266 insertions(+), 29 deletions(-)
create mode 100644 Documentation/netlink/specs/nlctrl.yaml
--
2.42.0
next reply other threads:[~2024-03-06 23:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 23:10 Donald Hunter [this message]
2024-03-06 23:10 ` [PATCH net-next v3 1/6] tools/net/ynl: Fix extack decoding for netlink-raw Donald Hunter
2024-03-06 23:10 ` [PATCH net-next v3 2/6] tools/net/ynl: Report netlink errors without stacktrace Donald Hunter
2024-03-07 9:31 ` Breno Leitao
2024-03-07 11:56 ` Donald Hunter
2024-03-07 15:58 ` Jakub Kicinski
2024-03-08 18:27 ` Breno Leitao
2024-03-08 19:16 ` Jakub Kicinski
2024-03-06 23:10 ` [PATCH net-next v3 3/6] tools/net/ynl: Fix c codegen for array-nest Donald Hunter
2024-03-06 23:10 ` [PATCH net-next v3 4/6] tools/net/ynl: Add nest-type-value decoding Donald Hunter
2024-03-06 23:10 ` [PATCH net-next v3 5/6] doc/netlink: Allow empty enum-name in ynl specs Donald Hunter
2024-03-07 2:26 ` Jakub Kicinski
2024-03-07 9:08 ` Donald Hunter
2024-03-07 15:21 ` Jakub Kicinski
2024-03-06 23:10 ` [PATCH net-next v3 6/6] doc/netlink/specs: Add spec for nlctrl netlink family Donald Hunter
2024-03-08 5:00 ` [PATCH net-next v3 0/6] tools/net/ynl: Add support " 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=20240306231046.97158-1-donald.hunter@gmail.com \
--to=donald.hunter@gmail.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@redhat.com \
--cc=edumazet@google.com \
--cc=jacob.e.keller@intel.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@google.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).