From: patchwork-bot+netdevbpf@kernel.org
To: Antonio Quartulli <antonio@openvpn.net>
Cc: netdev@vger.kernel.org, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, donald.hunter@gmail.com, ralf@mandelbit.com
Subject: Re: [PATCH net-next] tools: ynl: add uns-admin-perm to genetlink
Date: Fri, 06 Mar 2026 03:32:59 +0000 [thread overview]
Message-ID: <177276797904.3348267.3036793401644152557.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260304141020.23270-1-antonio@openvpn.net>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 4 Mar 2026 15:10:09 +0100 you wrote:
> GENL_UNS_ADMIN_PERM may be required by protocols using
> the `genetlink` family, however, this flag is currently
> only allowed in `genetlink-legacy`.
>
> Add it to the list of possible values in genetlink.yaml too.
>
> Cc: Simon Horman <horms@kernel.org>
> Cc: Donald Hunter <donald.hunter@gmail.com>
> Link: https://github.com/OpenVPN/ovpn-net-next/issues/33
> Suggested-by: Ralf Lici <ralf@mandelbit.com>
> Signed-off-by: Antonio Quartulli <antonio@openvpn.net>
>
> [...]
Here is the summary with links:
- [net-next] tools: ynl: add uns-admin-perm to genetlink
https://git.kernel.org/netdev/net-next/c/e5e09233e8a9
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:[~2026-03-06 3:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 14:10 [PATCH net-next] tools: ynl: add uns-admin-perm to genetlink Antonio Quartulli
2026-03-05 11:36 ` Donald Hunter
2026-03-05 15:04 ` Jakub Kicinski
2026-03-06 3:32 ` 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=177276797904.3348267.3036793401644152557.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=antonio@openvpn.net \
--cc=donald.hunter@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ralf@mandelbit.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