From: Jakub Kicinski <kuba@kernel.org>
To: Donald Hunter <donald.hunter@gmail.com>
Cc: Antonio Quartulli <antonio@openvpn.net>,
netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>, Ralf Lici <ralf@mandelbit.com>
Subject: Re: [PATCH net-next] tools: ynl: add uns-admin-perm to genetlink
Date: Thu, 5 Mar 2026 07:04:57 -0800 [thread overview]
Message-ID: <20260305070457.6b032e92@kernel.org> (raw)
In-Reply-To: <m2qzpyik31.fsf@gmail.com>
On Thu, 05 Mar 2026 11:36:50 +0000 Donald Hunter wrote:
> Though I see that genetlink-c is not actually referenced by any specs
> today so maybe we don't need it. I defer to Jakub for guidance.
I think it came up in the past, I'm fine with deleting it.
next prev parent reply other threads:[~2026-03-05 15:04 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 [this message]
2026-03-06 3:32 ` patchwork-bot+netdevbpf
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=20260305070457.6b032e92@kernel.org \
--to=kuba@kernel.org \
--cc=antonio@openvpn.net \
--cc=donald.hunter@gmail.com \
--cc=horms@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