From: Jakub Kicinski <kuba@kernel.org>
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Donald Hunter <donald.hunter@gmail.com>,
Jiri Pirko <jiri@resnulli.us>,
Jacob Keller <jacob.e.keller@intel.com>,
Stanislav Fomichev <sdf@google.com>
Subject: Re: [PATCHv2 net-next 1/2] ynl: rename array-nest to indexed-array
Date: Fri, 29 Mar 2024 07:13:48 -0700 [thread overview]
Message-ID: <20240329071348.7d18ec1f@kernel.org> (raw)
In-Reply-To: <20240329065423.1736120-2-liuhangbin@gmail.com>
On Fri, 29 Mar 2024 14:54:22 +0800 Hangbin Liu wrote:
> Some implementations, like bonding, has nest array with same attr type.
> To support all kinds of entries under one nest array. As disscussed[1],
> let's rename array-nest to indexed-array, and assuming the value is
> a nest by passing the type via sub-type.
>
> [1] https://lore.kernel.org/netdev/20240312100105.16a59086@kernel.org/
> diff --git a/Documentation/userspace-api/netlink/genetlink-legacy.rst b/Documentation/userspace-api/netlink/genetlink-legacy.rst
> index 70a77387f6c4..1ee1647d0ee8 100644
> --- a/Documentation/userspace-api/netlink/genetlink-legacy.rst
> +++ b/Documentation/userspace-api/netlink/genetlink-legacy.rst
> @@ -46,10 +46,16 @@ For reference the ``multi-attr`` array may look like this::
>
> where ``ARRAY-ATTR`` is the array entry type.
>
> -array-nest
> +indexed-array
> ~~~~~~~~~~
Documentation/userspace-api/netlink/genetlink-legacy.rst:50: WARNING: Title underline too short.
indexed-array
~~~~~~~~~~
--
pw-bot: cr
next prev parent reply other threads:[~2024-03-29 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 6:54 [PATCHv2 net-next 0/2] ynl: rename array-nest to indexed-array Hangbin Liu
2024-03-29 6:54 ` [PATCHv2 net-next 1/2] " Hangbin Liu
2024-03-29 14:13 ` Jakub Kicinski [this message]
2024-03-29 6:54 ` [PATCHv2 net-next 2/2] ynl: support binary/u32 sub-type for indexed-array Hangbin Liu
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=20240329071348.7d18ec1f@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=jacob.e.keller@intel.com \
--cc=jiri@resnulli.us \
--cc=liuhangbin@gmail.com \
--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).