From: patchwork-bot+netdevbpf@kernel.org
To: Kubalewski@ci.codeaurora.org, Arkadiusz <arkadiusz.kubalewski@intel.com>
Cc: kuba@kernel.org, donald.hunter@gmail.com, netdev@vger.kernel.org,
davem@davemloft.net, pabeni@redhat.com, edumazet@google.com,
simon.horman@corigine.com
Subject: Re: [PATCH net-next v4 0/2] tools: ynl-gen: fix parse multi-attr enum attribute
Date: Wed, 26 Jul 2023 21:00:22 +0000 [thread overview]
Message-ID: <169040522264.7465.1154235051402673715.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230725101642.267248-1-arkadiusz.kubalewski@intel.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 25 Jul 2023 12:16:40 +0200 you wrote:
> Fix the issues with parsing enums in ynl.py script.
>
> v4->v5:
> - fix indent issue in _decode_binary()
>
> v3->v4:
> - decoding 'enum-as-flag' starts from 0 instead of enum's start-value
> - move back usage of _decode_enum() back to _decode_binary()
> - fix typo in commit message
>
> [...]
Here is the summary with links:
- [net-next,v5,1/2] tools: ynl-gen: fix enum index in _decode_enum(..)
https://git.kernel.org/netdev/net/c/d7ddf5f4269f
- [net-next,v5,2/2] tools: ynl-gen: fix parse multi-attr enum attribute
https://git.kernel.org/netdev/net/c/df15c15e6c98
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-07-26 21:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 10:16 [PATCH net-next v4 0/2] tools: ynl-gen: fix parse multi-attr enum attribute Arkadiusz Kubalewski
2023-07-25 10:16 ` [PATCH net-next v5 1/2] tools: ynl-gen: fix enum index in _decode_enum(..) Arkadiusz Kubalewski
2023-07-25 12:53 ` Donald Hunter
2023-07-25 10:16 ` [PATCH net-next v5 2/2] tools: ynl-gen: fix parse multi-attr enum attribute Arkadiusz Kubalewski
2023-07-25 12:56 ` Donald Hunter
2023-07-26 3:13 ` [PATCH net-next v4 0/2] " Jakub Kicinski
2023-07-26 21:00 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-24 10:25 Arkadiusz Kubalewski
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=169040522264.7465.1154235051402673715.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Kubalewski@ci.codeaurora.org \
--cc=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 \
--cc=simon.horman@corigine.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.