From: Greg KH <gregkh@linuxfoundation.org>
To: Mat Martineau <mathew.j.martineau@linux.intel.com>
Cc: stable@vger.kernel.org, matthieu.baerts@tessares.net,
pabeni@redhat.com, mptcp@lists.linux.dev
Subject: Re: [PATCH 5.10 0/4] mptcp: Stable backports for MPTCP request sock fixes
Date: Thu, 12 Jan 2023 13:50:44 +0100 [thread overview]
Message-ID: <Y8ACJJeUzvn3j9Rx@kroah.com> (raw)
In-Reply-To: <20230107014631.449550-1-mathew.j.martineau@linux.intel.com>
On Fri, Jan 06, 2023 at 05:46:27PM -0800, Mat Martineau wrote:
> Greg -
>
> Here are backports of the MPTCP patches, and one prerequisite, that
> recently failed to apply to the 5.10 stable tree. They prevent IPv6
> memory leaks with MPTCP.
All now queued up, thanks.
greg k-h
prev parent reply other threads:[~2023-01-12 12:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 1:46 [PATCH 5.10 0/4] mptcp: Stable backports for MPTCP request sock fixes Mat Martineau
2023-01-07 1:46 ` [PATCH 5.10 1/4] mptcp: mark ops structures as ro_after_init Mat Martineau
2023-01-12 12:56 ` Patch "mptcp: mark ops structures as ro_after_init" has been added to the 5.10-stable tree gregkh
2023-01-07 1:46 ` [PATCH 5.10 2/4] mptcp: remove MPTCP 'ifdef' in TCP SYN cookies Mat Martineau
2023-01-12 12:56 ` Patch "mptcp: remove MPTCP 'ifdef' in TCP SYN cookies" has been added to the 5.10-stable tree gregkh
2023-01-07 1:46 ` [PATCH 5.10 3/4] mptcp: dedicated request sock for subflow in v6 Mat Martineau
2023-01-12 12:56 ` Patch "mptcp: dedicated request sock for subflow in v6" has been added to the 5.10-stable tree gregkh
2023-01-07 1:46 ` [PATCH 5.10 4/4] mptcp: use proper req destructor for IPv6 Mat Martineau
2023-01-12 12:56 ` Patch "mptcp: use proper req destructor for IPv6" has been added to the 5.10-stable tree gregkh
2023-01-12 12:50 ` 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=Y8ACJJeUzvn3j9Rx@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=mathew.j.martineau@linux.intel.com \
--cc=matthieu.baerts@tessares.net \
--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 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.