[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230324205722.7b6a9e70@kernel.org>
Date: Fri, 24 Mar 2023 20:57:22 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Donald Hunter <donald.hunter@...il.com>
Cc: netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Paolo Abeni <pabeni@...hat.com>,
Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org,
donald.hunter@...hat.com
Subject: Re: [PATCH net-next v4 7/7] docs: netlink: document the sub-type
attribute property
On Fri, 24 Mar 2023 19:19:00 +0000 Donald Hunter wrote:
> +sub-type
> +~~~~~~~~
> +
> +Attributes can have a ``sub-type`` that is interpreted in a ``type``
> +specific way. For example, an attribute with ``type: binary`` can have
> +``sub-type: u32`` which says to interpret the binary blob as an array of
> +``u32``. Binary types are described in more detail in
> +:doc:`genetlink-legacy`.
I think sub-type is only used for arrays? How about:
Legacy families have special ways of expressing arrays. ``sub-type``
can be used to define the type of array members in case array members
are not fully defined as attributes (in a bona fide attribute space).
For instance a C array of u32 values can be specified with
``type: binary`` and ``sub-type: u32``. Binary types and legacy array
formats are described in more detail in :doc:`genetlink-legacy`.
Powered by blists - more mailing lists