From: Greg KH <gregkh@linuxfoundation.org>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: tanggeliang@kylinos.cn, kuba@kernel.org, martineau@kernel.org,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] selftests: mptcp: rm subflow with v4/v4mapped addr" failed to apply to 6.1-stable tree
Date: Mon, 4 Mar 2024 11:58:41 +0100 [thread overview]
Message-ID: <2024030453-spotter-undermine-b600@gregkh> (raw)
In-Reply-To: <79f149f6-e5aa-455e-832e-8ae3356cb690@kernel.org>
On Mon, Mar 04, 2024 at 11:40:49AM +0100, Matthieu Baerts wrote:
> On 04/03/2024 11:32, Greg KH wrote:
> > On Mon, Mar 04, 2024 at 11:07:01AM +0100, Matthieu Baerts wrote:
> >> On 04/03/2024 09:30, gregkh@linuxfoundation.org wrote:
>
> (...)
>
> >>> ------------------ original commit in Linus's tree ------------------
> >>>
> >>> From 7092dbee23282b6fcf1313fc64e2b92649ee16e8 Mon Sep 17 00:00:00 2001
> >>> From: Geliang Tang <tanggeliang@kylinos.cn>
> >>> Date: Fri, 23 Feb 2024 17:14:12 +0100
> >>> Subject: [PATCH] selftests: mptcp: rm subflow with v4/v4mapped addr
> >>>
> >>> Now both a v4 address and a v4-mapped address are supported when
> >>> destroying a userspace pm subflow, this patch adds a second subflow
> >>> to "userspace pm add & remove address" test, and two subflows could
> >>> be removed two different ways, one with the v4mapped and one with v4.
> >> I don't think it is worth having this patch backported to v6.1: there
> >> are a lot of conflicts because this patch depends on many others. Also,
> >> many CIs validating stable trees will use the selftests from the last
> >> stable version, I suppose. So this new test will be validated on older
> >> versions.
> >>
> >> For v6.6 and v6.7, I can help to fix conflicts. I will just wait for the
> >> "queue/6.6" and "queue/6.7" branches to be updated with the latest
> >> patches :)
> >
> > Should all now be up to date,
>
> Maybe we are not talking about the same thing: are the "queue/X.Y"
> branches from the "linux-stable-rc" repo [1] not updated automatically
> when patches are added to the "stable-queue" repo [2]?
Ah, that, yeah, it somehow automagically works, I have no idea how it
does it or what controls it or who uses it, sorry :)
> It is just to know which base I use to resolve conflicts :)
If it works for you, great!
thanks
greg k-h
next prev parent reply other threads:[~2024-03-04 10:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 8:30 FAILED: patch "[PATCH] selftests: mptcp: rm subflow with v4/v4mapped addr" failed to apply to 6.1-stable tree gregkh
2024-03-04 10:07 ` Matthieu Baerts
2024-03-04 10:32 ` Greg KH
2024-03-04 10:40 ` Matthieu Baerts
2024-03-04 10:58 ` Greg KH [this message]
2024-03-04 11:32 ` 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=2024030453-spotter-undermine-b600@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tanggeliang@kylinos.cn \
/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