From: Stanislav Fomichev <stfomichev@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, donald.hunter@gmail.com,
netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com
Subject: Re: [PATCH net-next 0/3] tools: ynl: decode link types present in tests
Date: Mon, 6 Jan 2025 07:53:06 -0800 [thread overview]
Message-ID: <Z3v8Yn80sAL_qjIg@mini-arch> (raw)
In-Reply-To: <20250105012523.1722231-1-kuba@kernel.org>
On 01/04, Jakub Kicinski wrote:
> Using a kernel built for the net selftest target to run drivers/net
> tests currently fails, because the net kernel automatically spawns
> a handful of tunnel devices which YNL can't decode.
>
> Fill in those missing link types in rt_link. We need to extend subset
> support a bit for it to work.
>
> Jakub Kicinski (3):
> tools: ynl: correctly handle overrides of fields in subset
> tools: ynl: print some information about attribute we can't parse
> netlink: specs: rt_link: decode ip6tnl, vti and vti6 link attrs
>
> Documentation/netlink/specs/rt_link.yaml | 87 ++++++++++++++++++++++++
> tools/net/ynl/lib/nlspec.py | 5 +-
> tools/net/ynl/lib/ynl.py | 72 +++++++++++---------
> 3 files changed, 129 insertions(+), 35 deletions(-)
I've seen similar issues with (builtin) ip6tnl in my VMs, thanks for
fixing!
Acked-by: Stanislav Fomichev <sdf@fomichev.me>
prev parent reply other threads:[~2025-01-06 15:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-05 1:25 [PATCH net-next 0/3] tools: ynl: decode link types present in tests Jakub Kicinski
2025-01-05 1:25 ` [PATCH net-next 1/3] tools: ynl: correctly handle overrides of fields in subset Jakub Kicinski
2025-01-06 13:27 ` Donald Hunter
2025-01-06 15:36 ` Jakub Kicinski
2025-01-06 17:33 ` Donald Hunter
2025-01-05 1:25 ` [PATCH net-next 2/3] tools: ynl: print some information about attribute we can't parse Jakub Kicinski
2025-01-06 13:30 ` Donald Hunter
2025-01-05 1:25 ` [PATCH net-next 3/3] netlink: specs: rt_link: decode ip6tnl, vti and vti6 link attrs Jakub Kicinski
2025-01-06 13:38 ` Donald Hunter
2025-01-06 15:53 ` Stanislav Fomichev [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=Z3v8Yn80sAL_qjIg@mini-arch \
--to=stfomichev@gmail.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).