From: patchwork-bot+netdevbpf@kernel.org
To: Xu Du <xudu@redhat.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, shuah@kernel.org,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v6 0/7] selftest: Extend tun/virtio coverage for GSO over UDP tunnel
Date: Fri, 23 Jan 2026 19:50:32 +0000 [thread overview]
Message-ID: <176919783234.2695110.8587748919583568584.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1768979440.git.xudu@redhat.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 21 Jan 2026 18:04:54 +0800 you wrote:
> The design strategy is to extend the existing tun testing infrastructure
> to support this new use-case, rather than introducing a new or parallel framework.
> This allows for better integration and re-use of existing test logic.
>
> ---
> v5 -> v6:
> - Fix the Makefile format errors.
>
> [...]
Here is the summary with links:
- [net-next,v6,1/7] selftest: tun: Format tun.c existing code
https://git.kernel.org/netdev/net-next/c/e073c118db02
- [net-next,v6,2/7] selftest: tun: Introduce tuntap_helpers.h header for TUN/TAP testing
https://git.kernel.org/netdev/net-next/c/a942fcd72e97
- [net-next,v6,3/7] selftest: tun: Refactor tun_delete to use tuntap_helpers
https://git.kernel.org/netdev/net-next/c/82cfdcfa2010
- [net-next,v6,4/7] selftest: tun: Add helpers for GSO over UDP tunnel
https://git.kernel.org/netdev/net-next/c/24e59f26eef2
- [net-next,v6,5/7] selftest: tun: Add test for sending gso packet into tun
https://git.kernel.org/netdev/net-next/c/400e658aa096
- [net-next,v6,6/7] selftest: tun: Add test for receiving gso packet from tun
https://git.kernel.org/netdev/net-next/c/6bdd7ae6059e
- [net-next,v6,7/7] selftest: tun: Add test data for success and failure paths
https://git.kernel.org/netdev/net-next/c/87db2fdef5a7
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-01-23 19:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 10:04 [PATCH net-next v6 0/7] selftest: Extend tun/virtio coverage for GSO over UDP tunnel Xu Du
2026-01-21 10:04 ` [PATCH net-next v6 1/7] selftest: tun: Format tun.c existing code Xu Du
2026-01-21 10:04 ` [PATCH net-next v6 2/7] selftest: tun: Introduce tuntap_helpers.h header for TUN/TAP testing Xu Du
2026-01-21 10:04 ` [PATCH net-next v6 3/7] selftest: tun: Refactor tun_delete to use tuntap_helpers Xu Du
2026-01-21 10:04 ` [PATCH net-next v6 4/7] selftest: tun: Add helpers for GSO over UDP tunnel Xu Du
2026-01-23 19:43 ` Jakub Kicinski
2026-01-24 7:29 ` Xu Du
2026-01-21 10:04 ` [PATCH net-next v6 5/7] selftest: tun: Add test for sending gso packet into tun Xu Du
2026-01-21 10:05 ` [PATCH net-next v6 6/7] selftest: tun: Add test for receiving gso packet from tun Xu Du
2026-01-21 10:05 ` [PATCH net-next v6 7/7] selftest: tun: Add test data for success and failure paths Xu Du
2026-01-23 19:50 ` 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=176919783234.2695110.8587748919583568584.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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=xudu@redhat.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 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.