From: Sasha Levin <sashal@kernel.org>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: gregkh@linuxfoundation.org, jiayuan.chen@linux.dev,
stable-commits@vger.kernel.org,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
jakub@cloudflare.com, martin.lau@kernel.org
Subject: Re: Patch "mptcp: Fix proto fallback detection with BPF" has been added to the 6.1-stable tree
Date: Sat, 29 Nov 2025 15:57:29 -0500 [thread overview]
Message-ID: <aSteOTB6pHeXuXiF@laps> (raw)
In-Reply-To: <9e6ef98f-12eb-4608-aece-cf321e0a38d7@kernel.org>
On Fri, Nov 28, 2025 at 06:03:38PM +0100, Matthieu Baerts wrote:
>Hi Greg, Sasha, Jiayuan,
>
>On 27/11/2025 14:41, gregkh@linuxfoundation.org wrote:
>>
>> This is a note to let you know that I've just added the patch titled
>>
>> mptcp: Fix proto fallback detection with BPF
>>
>> to the 6.1-stable tree which can be found at:
>> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>>
>> The filename of the patch is:
>> mptcp-fix-proto-fallback-detection-with-bpf.patch
>> and it can be found in the queue-6.1 subdirectory.
>>
>> If you, or anyone else, feels it should not be added to the stable tree,
>> please let <stable@vger.kernel.org> know about it.
>
>@Sasha: thank you for having resolved the conflicts for this patch (and
>many others related to MPTCP recently). Sadly, it is causing troubles.
>
>@Greg/Sasha: is it possible to remove it from 6.1, 5.15 and 5.10 queues
>please?
>(The related patch in 6.6 and above is OK)
Dropped it from the older trees, thanks!
--
Thanks,
Sasha
next prev parent reply other threads:[~2025-11-29 20:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2025112711-frigidly-unruly-4a72@gregkh>
2025-11-28 17:03 ` Patch "mptcp: Fix proto fallback detection with BPF" has been added to the 6.1-stable tree Matthieu Baerts
2025-11-29 20:57 ` Sasha Levin [this message]
2025-11-30 3:09 ` Jiayuan Chen
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=aSteOTB6pHeXuXiF@laps \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jakub@cloudflare.com \
--cc=jiayuan.chen@linux.dev \
--cc=martin.lau@kernel.org \
--cc=matttbe@kernel.org \
--cc=stable-commits@vger.kernel.org \
--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