From: Paolo Abeni <pabeni@redhat.com>
To: mptcp@lists.linux.dev
Subject: [PATCH v2 mptcp-next 0/3] mptcp: add more mibs
Date: Fri, 14 Apr 2023 16:19:31 +0200 [thread overview]
Message-ID: <cover.1681481877.git.pabeni@redhat.com> (raw)
dumb cover letter for CI's sake.
Slould be applied only after the current tree has been crunched
by syzkaller for a little bit, as this will likely change quite
a bit the timings of some critical path, possibly hiding old races
and make more easy to reach other ones
Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/378
v1 -> v2:
- fix mpj self-tests failures
Paolo Abeni (3):
mptcp: introduces more address related mibs
selftests: mptcp: add explicit check for new mibs
selftests: mptcp: centralize stats dumping
net/mptcp/mib.c | 6 +
net/mptcp/mib.h | 18 +++
net/mptcp/options.c | 5 +-
net/mptcp/pm.c | 6 +-
.../testing/selftests/net/mptcp/mptcp_join.sh | 112 +++++++++---------
5 files changed, 91 insertions(+), 56 deletions(-)
--
2.39.2
next reply other threads:[~2023-04-14 14:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 14:19 Paolo Abeni [this message]
2023-04-14 14:19 ` [PATCH v2 mptcp-next 1/3] mptcp: introduces more address related mibs Paolo Abeni
2023-04-20 3:57 ` Geliang Tang
2023-04-20 10:18 ` Matthieu Baerts
2023-04-21 11:32 ` Matthieu Baerts
2023-04-14 14:19 ` [PATCH v2 mptcp-next 2/3] selftests: mptcp: add explicit check for new mibs Paolo Abeni
2023-04-21 11:32 ` Matthieu Baerts
2023-04-14 14:19 ` [PATCH v2 mptcp-next 3/3] selftests: mptcp: centralize stats dumping Paolo Abeni
2023-04-14 15:23 ` selftests: mptcp: centralize stats dumping: Tests Results MPTCP CI
2023-04-21 11:32 ` [PATCH v2 mptcp-next 0/3] mptcp: add more mibs Matthieu Baerts
2023-05-03 12:36 ` 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.1681481877.git.pabeni@redhat.com \
--to=pabeni@redhat.com \
--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 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.