From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
ncardwell@google.com, horms@kernel.org, kuniyu@google.com,
netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net-next 0/2] tcp: fix DSACK bug with non contiguous ranges
Date: Fri, 27 Jun 2025 22:50:14 +0000 [thread overview]
Message-ID: <175106461449.2081565.17099512582509919901.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250626123420.1933835-1-edumazet@google.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 26 Jun 2025 12:34:18 +0000 you wrote:
> This series combines a fix from xin.guo and a new packetdrill test.
>
> Eric Dumazet (1):
> selftests/net: packetdrill: add tcp_dsack_mult.pkt
>
> xin.guo (1):
> tcp: fix tcp_ofo_queue() to avoid including too much DUP SACK range
>
> [...]
Here is the summary with links:
- [net-next,1/2] tcp: fix tcp_ofo_queue() to avoid including too much DUP SACK range
https://git.kernel.org/netdev/net-next/c/a041f70e573e
- [net-next,2/2] selftests/net: packetdrill: add tcp_dsack_mult.pkt
https://git.kernel.org/netdev/net-next/c/8cc8d749dc7e
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:[~2025-06-27 22:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 12:34 [PATCH net-next 0/2] tcp: fix DSACK bug with non contiguous ranges Eric Dumazet
2025-06-26 12:34 ` [PATCH net-next 1/2] tcp: fix tcp_ofo_queue() to avoid including too much DUP SACK range Eric Dumazet
2025-06-26 12:34 ` [PATCH net-next 2/2] selftests/net: packetdrill: add tcp_dsack_mult.pkt Eric Dumazet
2025-06-27 22: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=175106461449.2081565.17099512582509919901.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@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;
as well as URLs for NNTP newsgroup(s).