From: patchwork-bot+netdevbpf@kernel.org
To: Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org, edumazet@google.com,
ncardwell@google.com, kuniyu@google.com, davem@davemloft.net,
dsahern@kernel.org, kuba@kernel.org, horms@kernel.org,
matttbe@kernel.org
Subject: Re: [PATCH v2 net-next 0/2] tcp: a couple of fixes
Date: Wed, 23 Jul 2025 01:30:39 +0000 [thread overview]
Message-ID: <175323423999.1016544.649440813048068442.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1753118029.git.pabeni@redhat.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 21 Jul 2025 19:20:20 +0200 you wrote:
> This series includes a couple of follow-up for the recent tcp receiver
> changes, addressing issues outlined by the nipa CI and the mptcp
> self-tests.
>
> Note that despite the affected self-tests where MPTCP ones, the issues
> are really in the TCP code, see patch 1 for the details.
>
> [...]
Here is the summary with links:
- [v2,net-next,1/2] tcp: do not set a zero size receive buffer
https://git.kernel.org/netdev/net-next/c/972ca7a3bc9a
- [v2,net-next,2/2] tcp: do not increment BeyondWindow MIB for old seq
https://git.kernel.org/netdev/net-next/c/b115c7758802
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-07-23 1:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 17:20 [PATCH v2 net-next 0/2] tcp: a couple of fixes Paolo Abeni
2025-07-21 17:20 ` [PATCH v2 net-next 1/2] tcp: do not set a zero size receive buffer Paolo Abeni
2025-07-21 18:21 ` Eric Dumazet
2025-07-21 17:20 ` [PATCH v2 net-next 2/2] tcp: do not increment BeyondWindow MIB for old seq Paolo Abeni
2025-07-23 1: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=175323423999.1016544.649440813048068442.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=matttbe@kernel.org \
--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 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.