From: Donald Hunter <donald.hunter@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
edumazet@google.com, pabeni@redhat.com
Subject: Re: [PATCH net-next 1/3] tools: ynl: correctly handle overrides of fields in subset
Date: Mon, 06 Jan 2025 13:27:49 +0000 [thread overview]
Message-ID: <m2a5c4nkbu.fsf@gmail.com> (raw)
In-Reply-To: <20250105012523.1722231-2-kuba@kernel.org> (Jakub Kicinski's message of "Sat, 4 Jan 2025 17:25:21 -0800")
Jakub Kicinski <kuba@kernel.org> writes:
> We stated in documentation [1] and previous discussions [2]
> that the need for overriding fields in members of subsets
> is anticipated. Implement it.
>
> [1] https://docs.kernel.org/next/userspace-api/netlink/specs.html#subset-of
> [2] https://lore.kernel.org/netdev/20231004171350.1f59cd1d@kernel.org/
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
I guess we're okay with requiring Python >= 3.9 for combining
dicts with |
Reviewed-by: Donald Hunter <donald.hunter@gmail.com>
> ---
> tools/net/ynl/lib/nlspec.py | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/tools/net/ynl/lib/nlspec.py b/tools/net/ynl/lib/nlspec.py
> index a745739655ad..314ec8007496 100644
> --- a/tools/net/ynl/lib/nlspec.py
> +++ b/tools/net/ynl/lib/nlspec.py
> @@ -219,7 +219,10 @@ jsonschema = None
> else:
> real_set = family.attr_sets[self.subset_of]
> for elem in self.yaml['attributes']:
> - attr = real_set[elem['name']]
> + real_attr = real_set[elem['name']]
> + combined_elem = real_attr.yaml | elem
> + attr = self.new_attr(combined_elem, real_attr.value)
> +
> self.attrs[attr.name] = attr
> self.attrs_by_val[attr.value] = attr
next prev parent reply other threads:[~2025-01-06 13:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-05 1:25 [PATCH net-next 0/3] tools: ynl: decode link types present in tests Jakub Kicinski
2025-01-05 1:25 ` [PATCH net-next 1/3] tools: ynl: correctly handle overrides of fields in subset Jakub Kicinski
2025-01-06 13:27 ` Donald Hunter [this message]
2025-01-06 15:36 ` Jakub Kicinski
2025-01-06 17:33 ` Donald Hunter
2025-01-05 1:25 ` [PATCH net-next 2/3] tools: ynl: print some information about attribute we can't parse Jakub Kicinski
2025-01-06 13:30 ` Donald Hunter
2025-01-05 1:25 ` [PATCH net-next 3/3] netlink: specs: rt_link: decode ip6tnl, vti and vti6 link attrs Jakub Kicinski
2025-01-06 13:38 ` Donald Hunter
2025-01-06 15:53 ` [PATCH net-next 0/3] tools: ynl: decode link types present in tests Stanislav Fomichev
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=m2a5c4nkbu.fsf@gmail.com \
--to=donald.hunter@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@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 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).