From: patchwork-bot+netdevbpf@kernel.org
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, shuah@kernel.org,
ast@kernel.org, daniel@iogearbox.net, hawk@kernel.org,
john.fastabend@gmail.com, toke@redhat.com, ignat@cloudflare.com,
linux-kselftest@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCHv2 net 0/2] selftests: Fix udpgro failures
Date: Mon, 19 Aug 2024 09:01:07 +0000 [thread overview]
Message-ID: <172405806778.469464.5030792856738166757.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240815075951.189059-1-liuhangbin@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 15 Aug 2024 15:59:49 +0800 you wrote:
> There are 2 issues for the current udpgro test. The first one is the testing
> doesn't record all the failures, which may report pass but the test actually
> failed. e.g.
> https://netdev-3.bots.linux.dev/vmksft-net/results/725661/45-udpgro-sh/stdout
>
> The other one is after commit d7db7775ea2e ("net: veth: do not manipulate
> GRO when using XDP"), there is no need to load xdp program to enable GRO
> on veth device.
>
> [...]
Here is the summary with links:
- [PATCHv2,net,1/2] selftests: udpgro: report error when receive failed
https://git.kernel.org/netdev/net/c/7167395a4be7
- [PATCHv2,net,2/2] selftests: udpgro: no need to load xdp for gro
https://git.kernel.org/netdev/net/c/d7818402b1d8
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:[~2024-08-19 9:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 7:59 [PATCHv2 net 0/2] selftests: Fix udpgro failures Hangbin Liu
2024-08-15 7:59 ` [PATCHv2 net 1/2] selftests: udpgro: report error when receive failed Hangbin Liu
2024-08-15 7:59 ` [PATCHv2 net 2/2] selftests: udpgro: no need to load xdp for gro Hangbin Liu
2024-08-19 9:01 ` 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=172405806778.469464.5030792856738166757.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=ignat@cloudflare.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=toke@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox