All of lore.kernel.org
 help / color / mirror / Atom feed
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>, Simon Horman <horms@kernel.org>,
	Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org
Cc: donald.hunter@redhat.com, Donald Hunter <donald.hunter@gmail.com>
Subject: [PATCH net-next v2 0/7] netlink: specs: add a spec for nl80211 wiphy
Date: Tue, 10 Dec 2024 16:14:41 +0000	[thread overview]
Message-ID: <20241210161448.76799-1-donald.hunter@gmail.com> (raw)

Add a rudimentary YNL spec for nl80211 that includes get-wiphy and
get-interface, along with some required enhancements to YNL and the
netlink schemas.

Patch 1 is a minor cleanup to prepare for patch 2
Patches 2-4 are new features for YNL
Patches 5-6 are schema updates for feature parity
Patch 7 is the new nl80211 spec

v1 -> v2
 - Add formatting hints support to patch 3, thanks Jakub
 - Raise exception for unhandled hints in patch 4, thanks Jakub
 - Update nl80211 spec w/ split-wiphy-dump in patch 7, thanks Johannes

Donald Hunter (7):
  tools/net/ynl: remove extraneous plural from variable names
  tools/net/ynl: support decoding indexed arrays as enums
  tools/net/ynl: support rendering C array members to strings
  tools/net/ynl: accept IP string inputs
  netlink: specs: support nested structs in genetlink legacy
  netlink: specs: add s8, s16 to genetlink schemas
  netlink: specs: wireless: add a spec for nl80211

 Documentation/netlink/genetlink-c.yaml      |    2 +-
 Documentation/netlink/genetlink-legacy.yaml |    5 +-
 Documentation/netlink/genetlink.yaml        |    2 +-
 Documentation/netlink/specs/nl80211.yaml    | 1938 +++++++++++++++++++
 tools/net/ynl/lib/ynl.py                    |   45 +-
 5 files changed, 1978 insertions(+), 14 deletions(-)
 create mode 100644 Documentation/netlink/specs/nl80211.yaml

-- 
2.47.1


             reply	other threads:[~2024-12-10 16:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-10 16:14 Donald Hunter [this message]
2024-12-10 16:14 ` [PATCH net-next v2 1/7] tools/net/ynl: remove extraneous plural from variable names Donald Hunter
2024-12-10 16:14 ` [PATCH net-next v2 2/7] tools/net/ynl: support decoding indexed arrays as enums Donald Hunter
2024-12-10 16:14 ` [PATCH net-next v2 3/7] tools/net/ynl: support rendering C array members to strings Donald Hunter
2024-12-10 16:14 ` [PATCH net-next v2 4/7] tools/net/ynl: accept IP string inputs Donald Hunter
2024-12-10 16:14 ` [PATCH net-next v2 5/7] netlink: specs: support nested structs in genetlink legacy Donald Hunter
2024-12-10 16:14 ` [PATCH net-next v2 6/7] netlink: specs: add s8, s16 to genetlink schemas Donald Hunter
2024-12-10 16:14 ` [PATCH net-next v2 7/7] netlink: specs: wireless: add a spec for nl80211 Donald Hunter
2024-12-11 21:07   ` Simon Horman
2024-12-11 22:24     ` Donald Hunter
2024-12-12  8:36   ` Johannes Berg
2024-12-18 14:32     ` Donald Hunter
2024-12-18 14:37       ` Johannes Berg

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=20241210161448.76799-1-donald.hunter@gmail.com \
    --to=donald.hunter@gmail.com \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@redhat.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=johannes@sipsolutions.net \
    --cc=kuba@kernel.org \
    --cc=linux-wireless@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 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.