From: Jakub Kicinski <kuba@kernel.org>
To: Anil Kaushik <anilkaushikwireless@gmail.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Harald Welte <laforge@gnumonks.org>,
Donald Hunter <donald.hunter@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
netdev@vger.kernel.org, osmocom-net-gprs@lists.osmocom.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC net-next] netlink: specs: add genetlink-legacy spec for GTP
Date: Wed, 7 Oct 2026 16:18:06 -0700 [thread overview]
Message-ID: <20261007161806.5fa99d43@kernel.org> (raw)
In-Reply-To: <20261001090250.3395779-1-anilkaushikwireless@gmail.com>
On Thu, 1 Oct 2026 09:02:50 +0000 Anil Kaushik wrote:
> The GTP (GPRS Tunnelling Protocol, user plane) generic netlink family
> has no YAML specification under Documentation/netlink/specs/, so it
> cannot be consumed by the ynl tooling used for user-space clients,
> documentation and selftests.
>
> Add a genetlink-legacy spec describing the existing family: the PDP
> context management commands (NEWPDP, DELPDP, GETPDP) and the GTP-U echo
> request (ECHOREQ), the GTPA_* attribute set, and the "gtp" multicast
> group. The spec is derived directly from include/uapi/linux/gtp.h and
> the gtp_genl_policy / gtp_genl_ops tables in drivers/net/gtp.c; command
> and attribute values match the existing uapi one-to-one.
>
> This only adds the description; there is no kernel code or uapi change.
Do you have any plans to use this?
Why send it as RFC and not PATCH?
next prev parent reply other threads:[~2026-10-07 23:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 9:02 [RFC net-next] netlink: specs: add genetlink-legacy spec for GTP Anil Kaushik
2026-10-07 23:18 ` Jakub Kicinski [this message]
2026-10-08 18:09 ` Anil Kaushik
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=20261007161806.5fa99d43@kernel.org \
--to=kuba@kernel.org \
--cc=anilkaushikwireless@gmail.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=laforge@gnumonks.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=osmocom-net-gprs@lists.osmocom.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.