From: Greg KH <gregkh@linuxfoundation.org>
To: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
Cc: stable@vger.kernel.org, MPTCP Upstream <mptcp@lists.linux.dev>,
Mat Martineau <martineau@kernel.org>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH 5.15.y] mptcp: pm: re-using ID of unused flushed subflows
Date: Sun, 8 Sep 2024 15:06:48 +0200 [thread overview]
Message-ID: <2024090839-passenger-preface-f0b7@gregkh> (raw)
In-Reply-To: <20240906082853.1764704-2-matttbe@kernel.org>
On Fri, Sep 06, 2024 at 10:28:54AM +0200, Matthieu Baerts (NGI0) wrote:
> commit ef34a6ea0cab1800f4b3c9c3c2cefd5091e03379 upstream.
>
I think I've got all of these now, thanks!
greg k-h
next prev parent reply other threads:[~2024-09-08 13:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 13:37 FAILED: patch "[PATCH] mptcp: pm: re-using ID of unused flushed subflows" failed to apply to 5.15-stable tree gregkh
2024-09-06 8:28 ` [PATCH 5.15.y] mptcp: pm: re-using ID of unused flushed subflows Matthieu Baerts (NGI0)
2024-09-08 13:06 ` Greg KH [this message]
2024-09-08 13:06 ` Patch "mptcp: pm: re-using ID of unused flushed subflows" has been added to the 5.15-stable tree gregkh
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=2024090839-passenger-preface-f0b7@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--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.