From: Geliang Tang <geliang.tang@linux.dev>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@linux.dev>
Subject: [PATCH mptcp-next 0/5] fixes for CURRESTAB
Date: Mon, 18 Dec 2023 16:47:12 +0800 [thread overview]
Message-ID: <cover.1702889134.git.geliang.tang@linux.dev> (raw)
Address Matt & Paolo's comments for CURRESTAB series.
Geliang Tang (5):
Squash to "mptcp: use mptcp_set_state" 1
mptcp: move inet_sk_state_store under lock
Squash to "mptcp: use mptcp_set_state" 2
Squash to "selftests: mptcp: check CURRESTAB counters"
selftests: mptcp: diag: check CURRESTAB counters
net/mptcp/pm_netlink.c | 16 +++++-----
tools/testing/selftests/net/mptcp/diag.sh | 30 +++++++++++++++++++
.../testing/selftests/net/mptcp/mptcp_join.sh | 5 ++--
3 files changed, 42 insertions(+), 9 deletions(-)
--
2.35.3
next reply other threads:[~2023-12-18 8:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 8:47 Geliang Tang [this message]
2023-12-18 8:47 ` [PATCH mptcp-next 1/5] Squash to "mptcp: use mptcp_set_state" 1 Geliang Tang
2023-12-18 8:47 ` [PATCH mptcp-next 2/5] mptcp: move inet_sk_state_store under lock Geliang Tang
2023-12-18 16:54 ` Paolo Abeni
2023-12-18 17:29 ` Matthieu Baerts
2023-12-19 7:57 ` Paolo Abeni
2023-12-19 8:05 ` Paolo Abeni
2023-12-19 12:38 ` Matthieu Baerts
2023-12-18 8:47 ` [PATCH mptcp-next 3/5] Squash to "mptcp: use mptcp_set_state" 2 Geliang Tang
2023-12-18 8:47 ` [PATCH mptcp-next 4/5] Squash to "selftests: mptcp: check CURRESTAB counters" Geliang Tang
2023-12-18 16:27 ` Matthieu Baerts
2023-12-18 8:47 ` [PATCH mptcp-next 5/5] selftests: mptcp: diag: check CURRESTAB counters Geliang Tang
2023-12-18 10:16 ` selftests: mptcp: diag: check CURRESTAB counters: Tests Results MPTCP CI
2023-12-18 16:22 ` [PATCH mptcp-next 5/5] selftests: mptcp: diag: check CURRESTAB counters Matthieu Baerts
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=cover.1702889134.git.geliang.tang@linux.dev \
--to=geliang.tang@linux.dev \
--cc=mptcp@lists.linux.dev \
/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