From: patchwork-bot+netdevbpf@kernel.org
To: Simon Baatz <gmbnomis@gmail.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] selftests/net: packetdrill: improve tcp_rcv_neg_window.pkt
Date: Thu, 19 Mar 2026 09:30:13 +0000 [thread overview]
Message-ID: <177391261329.1113925.12303763027691478280.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260316-improve_tcp_neg_usable_wnd_test-v1-1-f16d5e365107@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 16 Mar 2026 19:51:10 +0100 you wrote:
> From: Simon Baatz <gmbnomis@gmail.com>
>
> The test depends on accepting a packet that is larger than the
> advertised window and that does not trigger an immediate ACK.
>
> Previously, the test might still pass even if kernel behavior changed
> unexpectedly. Add assertions verifying that the large packet was
> accepted and no ACK was sent.
>
> [...]
Here is the summary with links:
- [net-next] selftests/net: packetdrill: improve tcp_rcv_neg_window.pkt
https://git.kernel.org/netdev/net-next/c/96a584db75bb
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-03-19 9:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 18:51 [PATCH net-next] selftests/net: packetdrill: improve tcp_rcv_neg_window.pkt Simon Baatz
2026-03-16 18:51 ` Simon Baatz via B4 Relay
2026-03-19 9:30 ` 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=177391261329.1113925.12303763027691478280.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gmbnomis@gmail.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 \
/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.