[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m27c3t33yu.fsf@gmail.com>
Date: Wed, 09 Apr 2025 13:38:01 +0100
From: Donald Hunter <donald.hunter@...il.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
pabeni@...hat.com, andrew+netdev@...n.ch, horms@...nel.org,
jacob.e.keller@...el.com, yuyanghuang@...gle.com, sdf@...ichev.me,
gnault@...hat.com, nicolas.dichtel@...nd.com, petrm@...dia.com
Subject: Re: [PATCH net-next 10/13] tools: ynl-gen: consider dump ops
without a do "type-consistent"
Jakub Kicinski <kuba@...nel.org> writes:
> If the type for the response to do and dump are the same we don't
> generate it twice. This is called "type_consistent" in the generator.
> Consider operations which only have dump to also be consistent.
> This removes unnecessary "_dump" from the names. There's a number
> of GET ops in classic Netlink which only have dump handlers.
>
> Signed-off-by: Jakub Kicinski <kuba@...nel.org>
> ---
> tools/net/ynl/pyynl/ynl_gen_c.py | 14 +++++++++-----
> 1 file changed, 9 insertions(+), 5 deletions(-)
>
> diff --git a/tools/net/ynl/pyynl/ynl_gen_c.py b/tools/net/ynl/pyynl/ynl_gen_c.py
> index b0b47a493a86..c97cda43a604 100755
> --- a/tools/net/ynl/pyynl/ynl_gen_c.py
> +++ b/tools/net/ynl/pyynl/ynl_gen_c.py
> @@ -1212,6 +1212,7 @@ from lib import SpecFamily, SpecAttrSet, SpecAttr, SpecOperation, SpecEnumSet, S
>
> # 'do' and 'dump' response parsing is identical
> self.type_consistent = True
> + self.type_onside = False
I'm not understanding what type_onside is meant to mean.
Powered by blists - more mailing lists