From: Matthieu Baerts <matttbe@kernel.org>
To: gregkh@linuxfoundation.org, Sasha Levin <sashal@kernel.org>
Cc: mptcp@lists.linux.dev, stable@vger.kernel.org
Subject: Re: [PATCH 6.6.y 0/2] Backport of "mptcp: pm: fix RM_ADDR ID for the initial subflow"
Date: Wed, 4 Sep 2024 14:56:57 +0200 [thread overview]
Message-ID: <d22f6a38-585f-4ec7-8c98-b5a1ebbceed2@kernel.org> (raw)
In-Reply-To: <20240903101654.3376356-4-matttbe@kernel.org>
Hi Greg, Sasha,
On 03/09/2024 12:16, Matthieu Baerts (NGI0) wrote:
> 87b5896f3f78 ("mptcp: pm: fix RM_ADDR ID for the initial subflow")
> depends on e38b117d7f3b ("mptcp: make pm_remove_addrs_and_subflows
> static") to avoid conflicts. Both can be backported to v6.6 without
> conflicts.
>
> If you prefer, feel free to backport these commits to v6.6:
>
> e38b117d7f3b 87b5896f3f78
>
> Details:
>
> - e38b117d7f3b ("mptcp: make pm_remove_addrs_and_subflows static")
> - 87b5896f3f78 ("mptcp: pm: fix RM_ADDR ID for the initial subflow")
FYI, Sasha has recently queued these 2 patches for v6.6. Nothing else
needs to be done here.
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2024-09-04 12:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 10:22 FAILED: patch "[PATCH] mptcp: pm: fix RM_ADDR ID for the initial subflow" failed to apply to 6.6-stable tree gregkh
2024-09-03 10:16 ` [PATCH 6.6.y 0/2] Backport of "mptcp: pm: fix RM_ADDR ID for the initial subflow" Matthieu Baerts (NGI0)
2024-09-04 12:56 ` Matthieu Baerts [this message]
2024-09-03 10:16 ` [PATCH 6.6.y 1/2] mptcp: make pm_remove_addrs_and_subflows static Matthieu Baerts (NGI0)
2024-09-03 10:16 ` [PATCH 6.6.y 2/2] mptcp: pm: fix RM_ADDR ID for the initial subflow Matthieu Baerts (NGI0)
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=d22f6a38-585f-4ec7-8c98-b5a1ebbceed2@kernel.org \
--to=matttbe@kernel.org \
--cc=gregkh@linuxfoundation.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