From: patchwork-bot+netdevbpf@kernel.org
To: Jason Xing <kerneljasonxing@gmail.com>
Cc: edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
davem@davemloft.net, dsahern@kernel.org, matttbe@kernel.org,
martineau@kernel.org, geliang@kernel.org, netdev@vger.kernel.org,
mptcp@lists.linux.dev, kernelxing@tencent.com
Subject: Re: [PATCH net v5 0/2] tcp/mptcp: count CLOSE-WAIT for CurrEstab
Date: Wed, 05 Jun 2024 11:40:28 +0000 [thread overview]
Message-ID: <171758762881.21278.4160920123722638055.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240603170217.6243-1-kerneljasonxing@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Tue, 4 Jun 2024 01:02:15 +0800 you wrote:
> From: Jason Xing <kernelxing@tencent.com>
>
> Taking CLOSE-WAIT sockets into CurrEstab counters is in accordance with RFC
> 1213, as suggested by Eric and Neal.
>
> v5
> Link: https://lore.kernel.org/all/20240531091753.75930-1-kerneljasonxing@gmail.com/
> 1. add more detailed comment (Matthieu)
>
> [...]
Here is the summary with links:
- [net,v5,1/2] tcp: count CLOSE-WAIT sockets for TCP_MIB_CURRESTAB
https://git.kernel.org/netdev/net/c/a46d0ea5c942
- [net,v5,2/2] mptcp: count CLOSE-WAIT sockets for MPTCP_MIB_CURRESTAB
https://git.kernel.org/netdev/net/c/9633e9377e6a
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-06-05 11:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 17:02 [PATCH net v5 0/2] tcp/mptcp: count CLOSE-WAIT for CurrEstab Jason Xing
2024-06-03 17:02 ` [PATCH net v5 1/2] tcp: count CLOSE-WAIT sockets for TCP_MIB_CURRESTAB Jason Xing
2024-06-03 17:02 ` [PATCH net v5 2/2] mptcp: count CLOSE-WAIT sockets for MPTCP_MIB_CURRESTAB Jason Xing
2024-06-03 19:48 ` Matthieu Baerts
2024-06-05 11: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=171758762881.21278.4160920123722638055.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=kerneljasonxing@gmail.com \
--cc=kernelxing@tencent.com \
--cc=kuba@kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--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).