From: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
To: mptcp@lists.linux.dev, stable@vger.kernel.org,
gregkh@linuxfoundation.org
Cc: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
Subject: [PATCH 6.1.y 0/2] mptcp: pm: only set fullmesh for subflow endp (and more)
Date: Sun, 9 Feb 2025 18:48:29 +0100 [thread overview]
Message-ID: <20250209174828.3397229-4-matttbe@kernel.org> (raw)
In-Reply-To: <2025020435-eagle-precision-e8dd@gregkh>
The commit 1bb0d1348546 ("mptcp: pm: only set fullmesh for subflow endp")
could not be backported to this kernel version without conflicts. Here
is an updated version adapted for this kernel version.
While at it, I also added the backport of the commit 56b824eb49d6
("mptcp: prevent excessive coalescing on receive") that we asked to
delay. There were no conflicts.
Matthieu Baerts (NGI0) (1):
mptcp: pm: only set fullmesh for subflow endp
Paolo Abeni (1):
mptcp: prevent excessive coalescing on receive
net/mptcp/pm_netlink.c | 3 ++-
net/mptcp/protocol.c | 1 +
2 files changed, 3 insertions(+), 1 deletion(-)
--
2.47.1
next prev parent reply other threads:[~2025-02-09 17:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 17:51 FAILED: patch "[PATCH] mptcp: pm: only set fullmesh for subflow endp" failed to apply to 6.1-stable tree gregkh
2025-02-09 17:48 ` Matthieu Baerts (NGI0) [this message]
2025-02-09 17:48 ` [PATCH 6.1.y 1/2] mptcp: pm: only set fullmesh for subflow endp Matthieu Baerts (NGI0)
2025-02-13 13:14 ` Patch "mptcp: pm: only set fullmesh for subflow endp" has been added to the 6.1-stable tree gregkh
2025-02-09 17:48 ` [PATCH 6.1.y 2/2] mptcp: prevent excessive coalescing on receive Matthieu Baerts (NGI0)
2025-02-13 13:14 ` Patch "mptcp: prevent excessive coalescing on receive" has been added to the 6.1-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=20250209174828.3397229-4-matttbe@kernel.org \
--to=matttbe@kernel.org \
--cc=gregkh@linuxfoundation.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.