All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: Mat Martineau <martineau@kernel.org>,
	Geliang Tang <geliang@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Shuah Khan <shuah@kernel.org>,
	pabeni@redhat.com, stable-commits@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: Patch "selftests: mptcp: explicitly trigger the listener diag code-path" has been added to the 6.7-stable tree
Date: Tue, 19 Mar 2024 11:25:36 -0400	[thread overview]
Message-ID: <ZfmucN89q-5SL9H8@sashalap> (raw)
In-Reply-To: <07543c96-f3f4-4df8-b77c-3824d6f53f29@kernel.org>

On Tue, Mar 19, 2024 at 03:49:52PM +0100, Matthieu Baerts wrote:
>Hi Sasha,
>
>On 19/03/2024 00:00, Sasha Levin wrote:
>> This is a note to let you know that I've just added the patch titled
>>
>>     selftests: mptcp: explicitly trigger the listener diag code-path
>>
>> to the 6.7-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:
>>      selftests-mptcp-explicitly-trigger-the-listener-diag.patch
>> and it can be found in the queue-6.7 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.
>
>I do :)
>
>> commit 02dc7e7327bc1a3551665745a40029cf96d6a8e6
>> Author: Paolo Abeni <pabeni@redhat.com>
>> Date:   Fri Feb 23 17:14:20 2024 +0100
>>
>>     selftests: mptcp: explicitly trigger the listener diag code-path
>>
>>     [ Upstream commit b4b51d36bbaa3ddb93b3e1ca3a1ef0aa629d6521 ]
>
>I think something went wrong: this patch was not supposed to be added to
>both 6.6 and 6.7 queues:
>
>  https://lore.kernel.org/stable/Zfg36tcGXUsZnJCh@sashalap/
>
>Do you mind dropping them from both queues, please?

Gah, sorry, I messed up. Now dropped.

-- 
Thanks,
Sasha

      reply	other threads:[~2024-03-19 15:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240318230045.2162042-1-sashal@kernel.org>
2024-03-19 14:49 ` Patch "selftests: mptcp: explicitly trigger the listener diag code-path" has been added to the 6.7-stable tree Matthieu Baerts
2024-03-19 15:25   ` Sasha Levin [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=ZfmucN89q-5SL9H8@sashalap \
    --to=sashal@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=geliang@kernel.org \
    --cc=kuba@kernel.org \
    --cc=martineau@kernel.org \
    --cc=matttbe@kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@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 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.