From: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
To: kuba@kernel.org, donald.hunter@gmail.com, netdev@vger.kernel.org,
davem@davemloft.net, pabeni@redhat.com, edumazet@google.com
Cc: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
Subject: [PATCH net-next v3 0/2] tools: ynl-gen: fix parse multi-attr enum attribute
Date: Tue, 18 Jul 2023 18:22:23 +0200 [thread overview]
Message-ID: <20230718162225.231775-1-arkadiusz.kubalewski@intel.com> (raw)
Fix the issues with parsing enums in ynl.py script.
v2->v3:
- Restore i iterator helper for decoding 'enum-as-flag' attributes in
_decode_enum(..) function.
- Fix _decode_enum(..) usage in case of binary & struct type attributes
by moving it to as_struct() funtion while calling _decode_enum(..) for
individual struct members.
v1->v2:
Initially this was one patch, but review shown there is need to fix also
leftover issues with indexing in _decode_enum(..) function
("tools: ynl-gen: fix enum index in _decode_enum(..)").
Arkadiusz Kubalewski (2):
tools: ynl-gen: fix enum index in _decode_enum(..)
tools: ynl-gen: fix parse multi-attr enum attribute
tools/net/ynl/lib/ynl.py | 24 ++++++++++++------------
1 file changed, 12 insertions(+), 12 deletions(-)
--
2.38.1
next reply other threads:[~2023-07-18 16:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 16:22 Arkadiusz Kubalewski [this message]
2023-07-18 16:22 ` [PATCH net-next v3 1/2] tools: ynl-gen: fix enum index in _decode_enum(..) Arkadiusz Kubalewski
2023-07-19 3:17 ` Jakub Kicinski
2023-07-19 21:09 ` Kubalewski, Arkadiusz
2023-07-21 8:54 ` Simon Horman
2023-07-25 10:20 ` Kubalewski, Arkadiusz
2023-07-18 16:22 ` [PATCH net-next v3 2/2] tools: ynl-gen: fix parse multi-attr enum attribute Arkadiusz Kubalewski
2023-07-19 3:19 ` Jakub Kicinski
2023-07-19 21:09 ` Kubalewski, Arkadiusz
2023-07-19 11:17 ` Donald Hunter
2023-07-19 21:08 ` Kubalewski, Arkadiusz
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=20230718162225.231775-1-arkadiusz.kubalewski@intel.com \
--to=arkadiusz.kubalewski@intel.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--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).