From: Greg KH <gregkh@linuxfoundation.org>
To: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev, stable@vger.kernel.org, sashal@kernel.org
Subject: Re: [PATCH 6.6.y 0/3] Backport of "mptcp: fix full TCP keep-alive support"
Date: Wed, 12 Jun 2024 14:52:41 +0200 [thread overview]
Message-ID: <2024061232-slinging-facsimile-d487@gregkh> (raw)
In-Reply-To: <20240529095817.3370953-5-matttbe@kernel.org>
On Wed, May 29, 2024 at 11:58:18AM +0200, Matthieu Baerts (NGI0) wrote:
> It looks like the patch "mptcp: fix full TCP keep-alive support" has
> been backported up to v6.8 recently (thanks!), but not before due to
> conflicts.
>
> I had to adapt a bit the code not to backport new features, but the
> modifications were simple, and isolated from the rest. MPTCP sockopt
> tests have been executed, and no issues have been reported.
>
> Matthieu Baerts (NGI0) (1):
> mptcp: fix full TCP keep-alive support
>
> Paolo Abeni (2):
> mptcp: avoid some duplicate code in socket option handling
> mptcp: cleanup SOL_TCP handling
>
> net/mptcp/protocol.h | 3 ++
> net/mptcp/sockopt.c | 123 +++++++++++++++++++++++++++++--------------
> 2 files changed, 87 insertions(+), 39 deletions(-)
>
> --
> 2.43.0
>
>
All backports now queued up, thanks so much for them!
greg k-h
prev parent reply other threads:[~2024-06-12 12:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 9:58 [PATCH 6.6.y 0/3] Backport of "mptcp: fix full TCP keep-alive support" Matthieu Baerts (NGI0)
2024-05-29 9:58 ` [PATCH 6.6.y 1/3] mptcp: avoid some duplicate code in socket option handling Matthieu Baerts (NGI0)
2024-05-29 9:58 ` [PATCH 6.6.y 2/3] mptcp: cleanup SOL_TCP handling Matthieu Baerts (NGI0)
2024-05-29 9:58 ` [PATCH 6.6.y 3/3] mptcp: fix full TCP keep-alive support Matthieu Baerts (NGI0)
2024-06-12 12:52 ` 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=2024061232-slinging-facsimile-d487@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=sashal@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox