All of lore.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.1.y 0/3] selftests: mptcp: fix backport issues
Date: Thu,  5 Sep 2024 16:43:07 +0200	[thread overview]
Message-ID: <20240905144306.1192409-5-matttbe@kernel.org> (raw)
In-Reply-To: <220913e1-603f-4399-a595-bb602942161a@kernel.org>

Greg recently reported that two of the backport patches I sent for v6.1
could not be applied [1][2]. It looks like it was because some other
patches have been applied twice, using different versions [3].

After having dropped the duplicated patches, the backport patches that 
couldn't be applied were still causing issues. It looks like it is due 
to quilt/patch having applied some code at the wrong place. This is 
fixed in patch 1/3. After that, the same two patches can be applied 
without any issue. They have been added in this series to help just in 
case.

Link: https://lore.kernel.org/2024090455-precook-unplanned-52b3@gregkh [1]
Link: https://lore.kernel.org/2024090420-passivism-garage-f753@gregkh [2]
Link: https://lore.kernel.org/fc21db4a-508d-41db-aa45-e3bc06d18ce7@kernel.org [3]

Matthieu Baerts (NGI0) (3):
  selftests: mptcp: fix backport issues
  selftests: mptcp: join: validate event numbers
  selftests: mptcp: join: check re-re-adding ID 0 signal

 .../testing/selftests/net/mptcp/mptcp_join.sh | 234 ++++++++++++------
 .../testing/selftests/net/mptcp/mptcp_lib.sh  |  15 ++
 2 files changed, 180 insertions(+), 69 deletions(-)

-- 
2.45.2


  reply	other threads:[~2024-09-05 14:44 UTC|newest]

Thread overview: 17+ 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.1-stable tree gregkh
2024-09-04 11:13 ` [PATCH 6.1.y] selftests: mptcp: join: validate event numbers Matthieu Baerts (NGI0)
2024-09-04 14:38   ` Greg KH
2024-09-04 15:20     ` Matthieu Baerts
2024-09-05  9:33       ` Greg KH
2024-09-05  9:36         ` Greg KH
2024-09-05  9:42           ` Matthieu Baerts
2024-09-05 10:10             ` Greg KH
2024-09-05 10:13               ` Matthieu Baerts
2024-09-05 14:43                 ` Matthieu Baerts (NGI0) [this message]
2024-09-08 14:03                   ` [PATCH 6.1.y 0/3] selftests: mptcp: fix backport issues Greg KH
2024-09-05 14:43                 ` [PATCH 6.1.y 1/3] " Matthieu Baerts (NGI0)
2024-09-08 14:03                   ` Patch "selftests: mptcp: fix backport issues" has been added to the 6.1-stable tree gregkh
2024-09-05 14:43                 ` [PATCH 6.1.y 2/3] selftests: mptcp: join: validate event numbers Matthieu Baerts (NGI0)
2024-09-08 14:03                   ` Patch "selftests: mptcp: join: validate event numbers" has been added to the 6.1-stable tree gregkh
2024-09-05 14:43                 ` [PATCH 6.1.y 3/3] selftests: mptcp: join: check re-re-adding ID 0 signal Matthieu Baerts (NGI0)
2024-09-08 14:03                   ` Patch "selftests: mptcp: join: check re-re-adding ID 0 signal" has been added to the 6.1-stable tree gregkh

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=20240905144306.1192409-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 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.