From: Matthieu Baerts <matttbe@kernel.org>
To: gregkh@linuxfoundation.org, geliang@kernel.org, pabeni@redhat.com
Cc: stable@vger.kernel.org, MPTCP Linux <mptcp@lists.linux.dev>
Subject: Re: FAILED: patch "[PATCH] selftests: mptcp: join: no extra msg if no counter" failed to apply to 5.10-stable tree
Date: Fri, 6 Sep 2024 10:26:22 +0200 [thread overview]
Message-ID: <646bcc1b-31db-4277-bd49-935c4ff387e5@kernel.org> (raw)
In-Reply-To: <2024083034-turret-available-e570@gregkh>
Hi Greg,
On 30/08/2024 12:27, gregkh@linuxfoundation.org wrote:
>
> The patch below does not apply to the 5.10-stable tree.
> If someone wants it applied there, or to any other stable or longterm
> tree, then please email the backport, including the original git commit
> id to <stable@vger.kernel.org>.
Thank you for the notification!
(...)
> ------------------ original commit in Linus's tree ------------------
>
> From 76a2d8394cc183df872adf04bf636eaf42746449 Mon Sep 17 00:00:00 2001
> From: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
> Date: Wed, 28 Aug 2024 08:14:31 +0200
> Subject: [PATCH] selftests: mptcp: join: no extra msg if no counter
>
> The checksum and fail counters might not be available. Then no need to
> display an extra message with missing info.
>
> While at it, fix the indentation around, which is wrong since the same
> commit.
>
> Fixes: 47867f0a7e83 ("selftests: mptcp: join: skip check if MIB counter not supported")
For the same reasons as the ones invoked for v5.15, no need to backport
this patch to v5.10.
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2024-09-06 8:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 10:27 FAILED: patch "[PATCH] selftests: mptcp: join: no extra msg if no counter" failed to apply to 5.10-stable tree gregkh
2024-09-06 8:26 ` Matthieu Baerts [this message]
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=646bcc1b-31db-4277-bd49-935c4ff387e5@kernel.org \
--to=matttbe@kernel.org \
--cc=geliang@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=mptcp@lists.linux.dev \
--cc=pabeni@redhat.com \
--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