From: Lorenzo Bianconi <lorenzo.bianconi@redhat.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] tools: ynl-gen: handle do ops with no input attrs
Date: Sat, 7 Oct 2023 10:26:40 +0200 [thread overview]
Message-ID: <ZSEWQM0Wdq2PJcLu@lore-desk> (raw)
In-Reply-To: <20231006135032.3328523-1-kuba@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2845 bytes --]
> The code supports dumps with no input attributes currently
> thru a combination of special-casing and luck.
> Clean up the handling of ops with no inputs. Create empty
> Structs, and skip printing of empty types.
> This makes dos with no inputs work.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> --
> CC: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
>
> Hi Lorenzo, the StructNone from my initial patch felt a little
> too hacky, so I ditched it :) Could you double check that this
> works the same as the previous version?
> ---
> tools/net/ynl/ynl-gen-c.py | 17 +++++++++++------
> 1 file changed, 11 insertions(+), 6 deletions(-)
Tested-by: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Regards,
Lorenzo
>
> diff --git a/tools/net/ynl/ynl-gen-c.py b/tools/net/ynl/ynl-gen-c.py
> index 168fe612b029..f125b5f704ba 100755
> --- a/tools/net/ynl/ynl-gen-c.py
> +++ b/tools/net/ynl/ynl-gen-c.py
> @@ -1041,9 +1041,11 @@ from lib import SpecFamily, SpecAttrSet, SpecAttr, SpecOperation, SpecEnumSet, S
> if op_mode == 'notify':
> op_mode = 'do'
> for op_dir in ['request', 'reply']:
> - if op and op_dir in op[op_mode]:
> - self.struct[op_dir] = Struct(family, self.attr_set,
> - type_list=op[op_mode][op_dir]['attributes'])
> + if op:
> + type_list = []
> + if op_dir in op[op_mode]:
> + type_list = op[op_mode][op_dir]['attributes']
> + self.struct[op_dir] = Struct(family, self.attr_set, type_list=type_list)
> if op_mode == 'event':
> self.struct['reply'] = Struct(family, self.attr_set, type_list=op['event']['attributes'])
>
> @@ -1752,6 +1754,8 @@ _C_KW = {
>
>
> def print_req_type_helpers(ri):
> + if len(ri.struct["request"].attr_list) == 0:
> + return
> print_alloc_wrapper(ri, "request")
> print_type_helpers(ri, "request")
>
> @@ -1773,6 +1777,8 @@ _C_KW = {
>
>
> def print_req_type(ri):
> + if len(ri.struct["request"].attr_list) == 0:
> + return
> print_type(ri, "request")
>
>
> @@ -2515,9 +2521,8 @@ _C_KW = {
> if 'dump' in op:
> cw.p(f"/* {op.enum_name} - dump */")
> ri = RenderInfo(cw, parsed, args.mode, op, 'dump')
> - if 'request' in op['dump']:
> - print_req_type(ri)
> - print_req_type_helpers(ri)
> + print_req_type(ri)
> + print_req_type_helpers(ri)
> if not ri.type_consistent:
> print_rsp_type(ri)
> print_wrapped_type(ri)
> --
> 2.41.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-10-07 8:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 13:50 [PATCH net-next] tools: ynl-gen: handle do ops with no input attrs Jakub Kicinski
2023-10-07 8:26 ` Lorenzo Bianconi [this message]
2023-10-10 2:50 ` patchwork-bot+netdevbpf
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=ZSEWQM0Wdq2PJcLu@lore-desk \
--to=lorenzo.bianconi@redhat.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).