public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
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/2] Backport of "selftests: mptcp: userspace_pm: fixed subtest names"
Date: Tue, 25 Jun 2024 18:22:10 +0200	[thread overview]
Message-ID: <20240625162209.3025306-4-matttbe@kernel.org> (raw)
In-Reply-To: <2024062405-railway-unpack-e903@gregkh>

Commit e874557fce1b ("selftests: mptcp: userspace_pm: fixed subtest
names") could not be applied in v6.6 tree, because commit 8ebb44196585
("selftests: mptcp: print_test out of verify_listener_events") was not
in v6.6.

We can backport this dependence: it is just a refactoring moving where
the listener test names are being printed in the selftests, no
conflicts. After having applied this dependence, the commit we were
initially interested by can also be applied without conflicts.

Geliang Tang (1):
  selftests: mptcp: print_test out of verify_listener_events

Matthieu Baerts (NGI0) (1):
  selftests: mptcp: userspace_pm: fixed subtest names

 .../selftests/net/mptcp/userspace_pm.sh       | 50 +++++++++++--------
 1 file changed, 28 insertions(+), 22 deletions(-)

-- 
2.43.0


  reply	other threads:[~2024-06-25 16:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-24 16:45 FAILED: patch "[PATCH] selftests: mptcp: userspace_pm: fixed subtest names" failed to apply to 6.6-stable tree gregkh
2024-06-25 16:22 ` Matthieu Baerts (NGI0) [this message]
2024-06-25 16:22 ` [PATCH 6.6.y 1/2] selftests: mptcp: print_test out of verify_listener_events Matthieu Baerts (NGI0)
2024-06-25 16:22 ` [PATCH 6.6.y 2/2] selftests: mptcp: userspace_pm: fixed subtest names 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=20240625162209.3025306-4-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