From: patchwork-bot+netdevbpf@kernel.org
To: Antonio Quartulli <antonio@openvpn.net>
Cc: netdev@vger.kernel.org, sd@queasysnail.net, ralf@mandelbit.com,
kuba@kernel.org, pabeni@redhat.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com
Subject: Re: [PATCH net-next 0/6] pull request: ovpn 2026-10-12
Date: Tue, 20 Oct 2026 02:20:06 +0000 [thread overview]
Message-ID: <179246280653.3441618.14893314533107061618.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261012133809.2477063-1-antonio@openvpn.net>
Hello:
This series was applied to netdev/net-next.git (main)
by Antonio Quartulli <antonio@openvpn.net>:
On Mon, 12 Oct 2026 15:37:57 +0200 you wrote:
> Hi all!
>
> Here is v4 of the ovpn batch for net-next.
>
> It is all cleanup and selftest work this time: no functional change to
> the driver. The selftests get TCP_NODELAY on ovpn-cli's TCP sockets and
> proper synchronization against the server-side key setup. Ralf is added
> to MAINTAINERS as ovpn reviewer.
>
> [...]
Here is the summary with links:
- [net-next,1/6] ovpn: Fix the return value in ovpn_bind_from_sockaddr() kernel-doc
https://git.kernel.org/netdev/net-next/c/c73695b5c297
- [net-next,2/6] ovpn: remove unused work field from struct ovpn_socket
https://git.kernel.org/netdev/net-next/c/1926cf58b0a8
- [net-next,3/6] ovpn: remove redundant peer NULL checks in crypto post functions
https://git.kernel.org/netdev/net-next/c/fbe0f8413514
- [net-next,4/6] selftests: ovpn: enable TCP_NODELAY on TCP sockets
https://git.kernel.org/netdev/net-next/c/5a5c645415c2
- [net-next,5/6] selftests: ovpn: wait for the TCP server key setup before traffic
https://git.kernel.org/netdev/net-next/c/03b7050e67e2
- [net-next,6/6] MAINTAINERS: ovpn: add Ralf Lici as reviewer
https://git.kernel.org/netdev/net-next/c/b2ed202907d6
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-20 2:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 13:37 [PATCH net-next 0/6] pull request: ovpn 2026-10-12 Antonio Quartulli
2026-10-12 13:37 ` [PATCH net-next 1/6] ovpn: Fix the return value in ovpn_bind_from_sockaddr() kernel-doc Antonio Quartulli
2026-10-12 13:37 ` [PATCH net-next 2/6] ovpn: remove unused work field from struct ovpn_socket Antonio Quartulli
2026-10-12 13:38 ` [PATCH net-next 3/6] ovpn: remove redundant peer NULL checks in crypto post functions Antonio Quartulli
2026-10-12 13:38 ` [PATCH net-next 4/6] selftests: ovpn: enable TCP_NODELAY on TCP sockets Antonio Quartulli
2026-10-13 14:39 ` netdev-bot+sashiko
2026-10-13 20:17 ` Antonio Quartulli
2026-10-12 13:38 ` [PATCH net-next 5/6] selftests: ovpn: wait for the TCP server key setup before traffic Antonio Quartulli
2026-10-13 14:39 ` netdev-bot+sashiko
2026-10-12 13:38 ` [PATCH net-next 6/6] MAINTAINERS: ovpn: add Ralf Lici as reviewer Antonio Quartulli
2026-10-20 2:17 ` [PATCH net-next 0/6] pull request: ovpn 2026-10-12 Jakub Kicinski
2026-10-20 2:20 ` 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=179246280653.3441618.14893314533107061618.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=antonio@openvpn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ralf@mandelbit.com \
--cc=sd@queasysnail.net \
/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