netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
	andrew+netdev@lunn.ch, horms@kernel.org, donald.hunter@gmail.com,
	johannes@sipsolutions.net, razor@blackwall.org,
	Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net-next v2 0/4] netlink: specs: remove phantom structs
Date: Tue,  6 May 2025 12:40:56 -0700	[thread overview]
Message-ID: <20250506194101.696272-1-kuba@kernel.org> (raw)

rt-netlink and nl80211 have a few structs which may be helpful for Python
decoding of binary attrs, but which don't actually exist in the C uAPI.
This prevents us from using struct pointers for binary types in C.

We could support this situation better in the codegen, or add these
structs to uAPI. That said Johannes suggested we remove the WiFi
structs for now, and the rt-link ones are semi-broken.
Drop the struct definitions, for now, if someone has a need to use
such structs in Python (as opposed to them being defined for completeness)
we can revist.

v2:
 - pure rebase
v1: https://lore.kernel.org/20250505170215.253672-1-kuba@kernel.org

Jakub Kicinski (4):
  netlink: specs: nl80211: drop structs which are not uAPI
  netlink: specs: ovs: correct struct names
  netlink: specs: remove implicit structs for SNMP counters
  netlink: specs: rt-link: remove implicit structs from devconf

 Documentation/netlink/specs/nl80211.yaml      |  68 -------
 Documentation/netlink/specs/ovs_datapath.yaml |  10 +-
 Documentation/netlink/specs/ovs_vport.yaml    |   5 +-
 Documentation/netlink/specs/rt-link.yaml      | 167 +++---------------
 4 files changed, 28 insertions(+), 222 deletions(-)

-- 
2.49.0


             reply	other threads:[~2025-05-06 19:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-06 19:40 Jakub Kicinski [this message]
2025-05-06 19:40 ` [PATCH net-next v2 1/4] netlink: specs: nl80211: drop structs which are not uAPI Jakub Kicinski
2025-05-06 19:40 ` [PATCH net-next v2 2/4] netlink: specs: ovs: correct struct names Jakub Kicinski
2025-05-06 19:40 ` [PATCH net-next v2 3/4] netlink: specs: remove implicit structs for SNMP counters Jakub Kicinski
2025-05-07 10:54   ` Donald Hunter
2025-05-06 19:41 ` [PATCH net-next v2 4/4] netlink: specs: rt-link: remove implicit structs from devconf Jakub Kicinski
2025-05-07 11:15   ` Donald Hunter
2025-05-08  1:40 ` [PATCH net-next v2 0/4] netlink: specs: remove phantom structs 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=20250506194101.696272-1-kuba@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=johannes@sipsolutions.net \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=razor@blackwall.org \
    /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).