From: patchwork-bot+netdevbpf@kernel.org
To: Anil Kaushik <anilkaushikwireless@gmail.com>
Cc: pablo@netfilter.org, laforge@gnumonks.org,
donald.hunter@gmail.com, kuba@kernel.org, davem@davemloft.net,
edumazet@kernel.org, pabeni@redhat.com, horms@kernel.org,
andrew+netdev@lunn.ch, shuah@kernel.org, sdf.kernel@gmail.com,
nicolas.dichtel@6wind.com, osmocom-net-gprs@lists.osmocom.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next v7 0/4] gtp: ynl spec for the GTP netlink family, two fixes, and a selftest
Date: Wed, 21 Oct 2026 10:00:07 +0000 [thread overview]
Message-ID: <179257680778.526483.7395011719912367177.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261016093225.1036375-1-anilkaushikwireless@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 16 Oct 2026 09:32:21 +0000 you wrote:
> This adds a ynl spec for the gtp genetlink family, two small driver
> fixes, and a selftest.
>
> Patch 1: the GET and dump replies carried the family id in the command
> field, so ynl dropped them. Use GTP_CMD_GETPDP instead.
> Patch 2: new in v7. On the netdev CI debug kernel, the selftest hit an
> RCU warning: adding a PDP context looks up the device without the RCU
> read lock. Hold it around the lookup.
> Patch 3: the spec (NEWPDP/DELPDP/GETPDP/ECHOREQ), no uapi change.
> Patch 4: a selftest that adds, dumps and deletes PDP contexts.
>
> [...]
Here is the summary with links:
- [net-next,v7,1/4] gtp: set a valid genl command in PDP context get and dump replies
https://git.kernel.org/netdev/net-next/c/758d8928d2c5
- [net-next,v7,2/4] gtp: hold RCU for the device lookup when adding a PDP context
https://git.kernel.org/netdev/net-next/c/fe3e1a42fb7e
- [net-next,v7,3/4] netlink: specs: add genetlink-legacy spec for GTP
https://git.kernel.org/netdev/net-next/c/8a2f9964fc28
- [net-next,v7,4/4] selftests: net: add a test for the gtp netlink family
https://git.kernel.org/netdev/net-next/c/ffb51f75013f
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-10-21 10:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 9:32 Anil Kaushik
2026-10-16 9:32 ` [PATCH net-next v7 1/4] gtp: set a valid genl command in PDP context get and dump replies Anil Kaushik
2026-10-16 9:32 ` [PATCH net-next v7 2/4] gtp: hold RCU for the device lookup when adding a PDP context Anil Kaushik
2026-10-16 9:32 ` [PATCH net-next v7 3/4] netlink: specs: add genetlink-legacy spec for GTP Anil Kaushik
2026-10-16 9:32 ` [PATCH net-next v7 4/4] selftests: net: add a test for the gtp netlink family Anil Kaushik
2026-10-21 10:00 ` 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=179257680778.526483.7395011719912367177.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=anilkaushikwireless@gmail.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=laforge@gnumonks.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=osmocom-net-gprs@lists.osmocom.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=sdf.kernel@gmail.com \
--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
all inboxes | Powered by JetHome®