From: Matthieu Baerts <matttbe@kernel.org>
To: MPTCP Linux <mptcp@lists.linux.dev>
Subject: Re: [PATCH mptcp-next 0/4] Fixes for "mptcp: pm: drop TCP TS with ADD_ADDRv6 + port"
Date: Tue, 2 Jun 2026 16:31:23 +1000 [thread overview]
Message-ID: <1294ddc5-94ec-4667-8765-baa184df0f32@kernel.org> (raw)
In-Reply-To: <20260601-mptcp-add-addr6-port-ts-fixes-v2-v1-0-d7c842e80446@kernel.org>
Hello,
On 01/06/2026 18:27, Matthieu Baerts (NGI0) wrote:
> This address Eric's comments from [1].
>
> Note that the CI will complain that not each patch can be built
> individually. That's normal: the fix from patch 2 has to be split in
> patch 3, to be applied in the right commit.
I'm going to apply patches 1-3, because they have been requested by
Eric, I guess that's fine. After that, I will apply Eric's patch [1]
with the small fix in our tree, resolve conflicts, and send an extra fix.
[1] https://lore.kernel.org/20260601091816.444738-1-edumazet@google.com
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2026-06-02 6:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 8:27 [PATCH mptcp-next 0/4] Fixes for "mptcp: pm: drop TCP TS with ADD_ADDRv6 + port" Matthieu Baerts (NGI0)
2026-06-01 8:27 ` [PATCH mptcp-next 1/4] Squash to: "mptcp: introduce add_addr_v6_port_drop_ts sysctl knob" Matthieu Baerts (NGI0)
2026-06-01 8:27 ` [PATCH mptcp-next 2/4] Squash to "tcp: allow mptcp to drop TS for some packets" Matthieu Baerts (NGI0)
2026-06-01 8:27 ` [PATCH mptcp-next 3/4] Squash to "mptcp: pm: drop TCP TS with ADD_ADDRv6 + port" Matthieu Baerts (NGI0)
2026-06-01 8:27 ` [PATCH mptcp-next 4/4] mptcp: use READ_ONCE() over sysctls Matthieu Baerts (NGI0)
2026-07-02 5:37 ` Geliang Tang
2026-06-01 9:04 ` [PATCH mptcp-next 0/4] Fixes for "mptcp: pm: drop TCP TS with ADD_ADDRv6 + port" MPTCP CI
2026-06-01 9:54 ` MPTCP CI
2026-06-02 6:31 ` Matthieu Baerts [this message]
2026-06-02 6:59 ` Matthieu Baerts
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=1294ddc5-94ec-4667-8765-baa184df0f32@kernel.org \
--to=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
/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