From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, kuba@kernel.org, pabeni@redhat.com,
davem@davemloft.net, edumazet@google.com
Subject: Re: [patch net-next v4] tools: ynl: introduce option to process unknown attributes or types
Date: Fri, 27 Oct 2023 22:00:23 +0000 [thread overview]
Message-ID: <169844402397.23229.13480254568507181124.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231027092525.956172-1-jiri@resnulli.us>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 27 Oct 2023 11:25:25 +0200 you wrote:
> From: Jiri Pirko <jiri@nvidia.com>
>
> In case the kernel sends message back containing attribute not defined
> in family spec, following exception is raised to the user:
>
> $ sudo ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/devlink.yaml --do trap-get --json '{"bus-name": "netdevsim", "dev-name": "netdevsim1", "trap-name": "source_mac_is_multicast"}'
> Traceback (most recent call last):
> File "/home/jiri/work/linux/tools/net/ynl/lib/ynl.py", line 521, in _decode
> attr_spec = attr_space.attrs_by_val[attr.type]
> ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^
> KeyError: 132
>
> [...]
Here is the summary with links:
- [net-next,v4] tools: ynl: introduce option to process unknown attributes or types
https://git.kernel.org/netdev/net-next/c/d96e48a3d55d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-10-27 22:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 9:25 [patch net-next v4] tools: ynl: introduce option to process unknown attributes or types Jiri Pirko
2023-10-27 21:54 ` Jakub Kicinski
2023-10-28 8:24 ` Jiri Pirko
2023-10-27 22:00 ` patchwork-bot+netdevbpf [this message]
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=169844402397.23229.13480254568507181124.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--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).