From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
shuah@kernel.org, linux-kselftest@vger.kernel.org,
sdf@fomichev.me, willemb@google.com, petrm@nvidia.com
Subject: Re: [PATCH net-next v3 0/6] selftests: drv-net: gro: enable HW GRO and LRO testing
Date: Wed, 14 Jan 2026 02:40:16 +0000 [thread overview]
Message-ID: <176835841678.2561636.12391509152675295422.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260113000740.255360-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 12 Jan 2026 16:07:34 -0800 you wrote:
> Add support for running our existing GRO test against HW GRO
> and LRO implementation. The first 3 patches are just ksft lib
> nice-to-haves, and patch 4 cleans up the existing gro Python.
>
> Patches 5 and 6 are of most practical interest. The support
> reconfiguring the NIC to disable SW GRO and enable HW GRO and LRO.
> Additionally last patch breaks up the existing GRO cases to
> track HW compliance at finer granularity.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/6] selftests: net: py: teach ksft_pr() multi-line safety
https://git.kernel.org/netdev/net-next/c/b324192e36ec
- [net-next,v3,2/6] selftests: net: py: teach cmd() how to print itself
https://git.kernel.org/netdev/net-next/c/ce0f92dc737c
- [net-next,v3,3/6] selftests: drv-net: gro: use cmd print
https://git.kernel.org/netdev/net-next/c/d131da6d7282
- [net-next,v3,4/6] selftests: drv-net: gro: improve feature config
https://git.kernel.org/netdev/net-next/c/8171f6a76b22
- [net-next,v3,5/6] selftests: drv-net: gro: run the test against HW GRO and LRO
https://git.kernel.org/netdev/net-next/c/d3b35898de02
- [net-next,v3,6/6] selftests: drv-net: gro: break out all individual test cases
https://git.kernel.org/netdev/net-next/c/fe074aaa5329
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-14 2:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 0:07 [PATCH net-next v3 0/6] selftests: drv-net: gro: enable HW GRO and LRO testing Jakub Kicinski
2026-01-13 0:07 ` [PATCH net-next v3 1/6] selftests: net: py: teach ksft_pr() multi-line safety Jakub Kicinski
2026-01-13 0:07 ` [PATCH net-next v3 2/6] selftests: net: py: teach cmd() how to print itself Jakub Kicinski
2026-01-13 0:07 ` [PATCH net-next v3 3/6] selftests: drv-net: gro: use cmd print Jakub Kicinski
2026-01-13 0:07 ` [PATCH net-next v3 4/6] selftests: drv-net: gro: improve feature config Jakub Kicinski
2026-01-13 0:07 ` [PATCH net-next v3 5/6] selftests: drv-net: gro: run the test against HW GRO and LRO Jakub Kicinski
2026-01-13 0:07 ` [PATCH net-next v3 6/6] selftests: drv-net: gro: break out all individual test cases Jakub Kicinski
2026-01-14 2: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=176835841678.2561636.12391509152675295422.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=willemb@google.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