From: patchwork-bot+netdevbpf@kernel.org
To: Haishuang Yan <yanhaishuang@cmss.chinamobile.com>
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, shuah@kernel.org,
alice.kernel@fastmail.im, daniel@iogearbox.net,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v4 0/2] bareudp: Enable BIG TCP packets
Date: Sat, 17 Oct 2026 01:40:20 +0000 [thread overview]
Message-ID: <179220122001.1050340.14067419361177757492.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261011102023.1603595-1-yanhaishuang@cmss.chinamobile.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 11 Oct 2026 18:20:21 +0800 you wrote:
> This series allows BIG TCP on bareudp, the same way as on vxlan and
> geneve, and extends the big_tcp_tunnels.sh selftest to cover it.
>
> Patch 1 bumps tso_max_size of bareudp devices to GSO_MAX_SIZE.
>
> Patch 2 adds bareudp to big_tcp_tunnels.sh. bareudp only works in
> external mode, so the test attaches the tunnel metadata with a tc
> tunnel_key action on egress.
>
> [...]
Here is the summary with links:
- [net-next,v4,1/2] bareudp: Enable BIG TCP packets
https://git.kernel.org/netdev/net-next/c/1240de9e5120
- [net-next,v4,2/2] selftests: net: big_tcp_tunnels: Cover bareudp
https://git.kernel.org/netdev/net-next/c/3e3f209961b0
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-17 1:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-11 10:20 [PATCH net-next v4 0/2] bareudp: Enable BIG TCP packets Haishuang Yan
2026-10-11 10:20 ` [PATCH net-next v4 1/2] " Haishuang Yan
2026-10-16 19:10 ` Simon Horman
2026-10-11 10:20 ` [PATCH net-next v4 2/2] selftests: net: big_tcp_tunnels: Cover bareudp Haishuang Yan
2026-10-16 19:11 ` Simon Horman
2026-10-17 1:40 ` 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=179220122001.1050340.14067419361177757492.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alice.kernel@fastmail.im \
--cc=andrew+netdev@lunn.ch \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=yanhaishuang@cmss.chinamobile.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