Re: FAILED: patch "[PATCH] selftests: mptcp: pm: check flush doesn't reset limits" failed to apply to 5.10-stable tree

[Greg KH <gregkh@linuxfoundation.org>]

On Fri, Aug 22, 2025 at 04:43:13PM +0200, Matthieu Baerts wrote:
> Hi Greg,
> 
> On 22/08/2025 08:05, gregkh@linuxfoundation.org wrote:
> > 
> > The patch below does not apply to the 5.10-stable tree.
> 
> Thank you for the notification!
> 
> > ------------------ original commit in Linus's tree ------------------
> > 
> > From 452690be7de2f91cc0de68cb9e95252875b33503 Mon Sep 17 00:00:00 2001
> > From: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
> > Date: Fri, 15 Aug 2025 19:28:21 +0200
> > Subject: [PATCH] selftests: mptcp: pm: check flush doesn't reset limits
> > 
> > This modification is linked to the parent commit where the received
> > ADD_ADDR limit was accidentally reset when the endpoints were flushed.
> > 
> > To validate that, the test is now flushing endpoints after having set
> > new limits, and before checking them.
> > 
> > The 'Fixes' tag here below is the same as the one from the previous
> > commit: this patch here is not fixing anything wrong in the selftests,
> > but it validates the previous fix for an issue introduced by this commit
> > ID.
> 
> The upstream's parent patch has not been queued in v5.10 yet, but I
> already got this FAILED notification for this patch here. I guess some
> conflicts on your side prevent you to send the last batch of fixes for
> v5.10, but they will come at some points. I'm going to send a resolution
> for this backport here, because I have it: I hope that's OK.
> 
> (Worst case if this patch is applied and not the parent one: the
> selftests will complain the parent patch is missing, which would serve
> as a reminder somehow, so that's probably OK :) )

Yes, sorry, I haven't caught up on pending 5.10.y patches yet, thanks
for the backport.

greg k-h