Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
Cc: stable@vger.kernel.org, "MPTCP Upstream" <mptcp@lists.linux.dev>,
	"Arınç ÜNAL" <arinc.unal@arinc9.com>,
	"Mat Martineau" <martineau@kernel.org>,
	"Paolo Abeni" <pabeni@redhat.com>
Subject: Re: [PATCH 6.1.y] mptcp: avoid duplicated SUB_CLOSED events
Date: Wed, 4 Sep 2024 16:34:29 +0200	[thread overview]
Message-ID: <2024090425-sneer-driver-0763@gregkh> (raw)
In-Reply-To: <20240904111113.4092725-2-matttbe@kernel.org>

On Wed, Sep 04, 2024 at 01:11:14PM +0200, Matthieu Baerts (NGI0) wrote:
> commit d82809b6c5f2676b382f77a5cbeb1a5d91ed2235 upstream.
> 

Applied

      reply	other threads:[~2024-09-04 14:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-30 10:23 FAILED: patch "[PATCH] mptcp: avoid duplicated SUB_CLOSED events" failed to apply to 6.1-stable tree gregkh
2024-09-04 11:11 ` [PATCH 6.1.y] mptcp: avoid duplicated SUB_CLOSED events Matthieu Baerts (NGI0)
2024-09-04 14:34   ` Greg KH [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=2024090425-sneer-driver-0763@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=arinc.unal@arinc9.com \
    --cc=martineau@kernel.org \
    --cc=matttbe@kernel.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