On Wed, 2024-12-18 at 14:32 +0000, Donald Hunter wrote: > > > > +operations: > > > + enum-model: directional > > > + list: > > > + - > > > + name: get-wiphy > > > + doc: | > > > + Get information about a wiphy or dump a list of all wiphys. Requests to dump get-wiphy > > > + should unconditionally include the split-wiphy-dump flag in the request. > > > + attribute-set: nl80211-attrs > > > + do: > > > + request: > > > + value: 1 > > > + attributes: > > > + - wiphy > > > + - wdev > > > + - ifindex > > > + reply: > > > + value: 3 > > > > could the value not reference "get-wiphy" and "new-wiphy" from the > > command list? That might be easier to understand? > > There is currently no schema or tool support for referencing enum > constants when defining protocol message ids. Most of the netlink > families don't have any need for an enumeration of commands in the > spec; nl80211 is unusual in reporting available commands. Oh, that's what it is. I'm not sure anyone really needs that now with the genetlink introspection, though I guess existing tools do use it. johannes
