From: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
To: mptcp@lists.linux.dev, stable@vger.kernel.org,
gregkh@linuxfoundation.org
Cc: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
Subject: [PATCH 6.6.y 0/3] Backport of "selftests: mptcp: join: validate event numbers" and more
Date: Tue, 3 Sep 2024 12:23:48 +0200 [thread overview]
Message-ID: <20240903102347.3384947-5-matttbe@kernel.org> (raw)
In-Reply-To: <2024083025-ruined-stupor-4967@gregkh>
To ease the inclusion of 20ccc7c5f7a3 ("selftests: mptcp: join: validate
event numbers"), 35bc143a8514 ("selftests: mptcp: add mptcp_lib_events
helper") sounds safe to be backported as well, even if there are some
small conflicts, but easy to resolve.
Once resolved, f18fa2abf810 ("selftests: mptcp: join: check re-re-adding
ID 0 signal") can be backported without any conflicts.
Geliang Tang (1):
selftests: mptcp: add mptcp_lib_events helper
Matthieu Baerts (NGI0) (2):
selftests: mptcp: join: validate event numbers
selftests: mptcp: join: check re-re-adding ID 0 signal
.../testing/selftests/net/mptcp/mptcp_join.sh | 100 +++++++++++++++---
.../testing/selftests/net/mptcp/mptcp_lib.sh | 27 +++++
.../selftests/net/mptcp/userspace_pm.sh | 14 +--
3 files changed, 117 insertions(+), 24 deletions(-)
--
2.45.2
next prev parent reply other threads:[~2024-09-03 10:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 10:28 FAILED: patch "[PATCH] selftests: mptcp: join: validate event numbers" failed to apply to 6.6-stable tree gregkh
2024-09-03 10:23 ` Matthieu Baerts (NGI0) [this message]
2024-09-04 14:18 ` [PATCH 6.6.y 0/3] Backport of "selftests: mptcp: join: validate event numbers" and more Greg KH
2024-09-03 10:23 ` [PATCH 6.6.y 1/3] selftests: mptcp: add mptcp_lib_events helper Matthieu Baerts (NGI0)
2024-09-03 10:23 ` [PATCH 6.6.y 2/3] selftests: mptcp: join: validate event numbers Matthieu Baerts (NGI0)
2024-09-03 10:23 ` [PATCH 6.6.y 3/3] selftests: mptcp: join: check re-re-adding ID 0 signal Matthieu Baerts (NGI0)
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=20240903102347.3384947-5-matttbe@kernel.org \
--to=matttbe@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=mptcp@lists.linux.dev \
--cc=stable@vger.kernel.org \
/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