From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, donald.hunter@gmail.com,
netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
andrew+netdev@lunn.ch, horms@kernel.org, shuah@kernel.org,
sdf@fomichev.me, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next 0/5] tools: ynl: policy query support
Date: Wed, 11 Mar 2026 02:40:21 +0000 [thread overview]
Message-ID: <177319682153.3014711.5472638473199917370.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260310005337.3594225-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 9 Mar 2026 17:53:32 -0700 you wrote:
> Improve the Netlink policy support in YNL. This series grew out of
> improvements to policy checking, when writing selftests I realized
> that instead of doing all the policy parsing in the test we're
> better off making it part of YNL itself.
>
> Patch 1 adds pad handling, apparently we never hit pad with commonly
> used families. nlctrl policy dumps use pad more frequently.
> Patch 2 is a trivial refactor.
> Patch 3 pays off some technical debt in terms of documentation.
> The YnlFamily class is growing in size and it's quite hard to
> find its members. So document it a little bit.
> Patch 4 is the main dish, the implementation of get_policy(op)
> in YnlFamily.
> Patch 5 plugs the new functionality into the CLI.
>
> [...]
Here is the summary with links:
- [net-next,1/5] tools: ynl: handle pad type during decode
https://git.kernel.org/netdev/net-next/c/7b1309c33927
- [net-next,2/5] tools: ynl: move policy decoding out of NlMsg
https://git.kernel.org/netdev/net-next/c/c26fda6212b8
- [net-next,3/5] tools: ynl: add short doc to class YnlFamily
https://git.kernel.org/netdev/net-next/c/8bbcfce5db97
- [net-next,4/5] tools: ynl: add Python API for easier access to policies
https://git.kernel.org/netdev/net-next/c/77a6401a8722
- [net-next,5/5] tools: ynl: cli: add --policy support
https://git.kernel.org/netdev/net-next/c/d6df5e9b2a56
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:[~2026-03-11 2:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 0:53 [PATCH net-next 0/5] tools: ynl: policy query support Jakub Kicinski
2026-03-10 0:53 ` [PATCH net-next 1/5] tools: ynl: handle pad type during decode Jakub Kicinski
2026-03-10 0:53 ` [PATCH net-next 2/5] tools: ynl: move policy decoding out of NlMsg Jakub Kicinski
2026-03-10 0:53 ` [PATCH net-next 3/5] tools: ynl: add short doc to class YnlFamily Jakub Kicinski
2026-03-10 0:53 ` [PATCH net-next 4/5] tools: ynl: add Python API for easier access to policies Jakub Kicinski
2026-03-10 0:53 ` [PATCH net-next 5/5] tools: ynl: cli: add --policy support Jakub Kicinski
2026-03-11 2:40 ` patchwork-bot+netdevbpf [this message]
2026-03-11 11:30 ` [PATCH net-next 0/5] tools: ynl: policy query support Donald Hunter
2026-03-11 18:35 ` Jakub Kicinski
2026-03-12 17:17 ` Donald Hunter
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=177319682153.3014711.5472638473199917370.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
/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