From: Matthieu Baerts <matttbe@kernel.org>
To: MPTCP Linux <mptcp@lists.linux.dev>
Subject: Re: [PATCH mptcp-next] Squash to "mptcp: better mptcp-level RTT estimator"
Date: Mon, 6 Apr 2026 16:18:44 +0200 [thread overview]
Message-ID: <950acce2-7369-4f83-9307-0131b99a3eff@kernel.org> (raw)
In-Reply-To: <20260403-mptcp-fix-better-mptcp-level-rtt-estimator-v1-1-b22152ecd69d@kernel.org>
Hello,
On 03/04/2026 13:34, Matthieu Baerts (NGI0) wrote:
> Address AI reviews:
>
> - samples[0] is read without READ_ONCE, while the others are.
>
> - prev_rtt_us is added but not used.
FYI, I just applied this patch, these comments have been previously
acked by Paolo, and the fixes were straightforward.
New patches for t/upstream:
- 1259cb662bb0: "squashed" in "mptcp: better mptcp-level RTT estimator"
- Results: e8056528d187..efc8256ccab0 (export)
Tests are now in progress:
- export:
https://github.com/multipath-tcp/mptcp_net-next/commit/40ddceaaadee57911993715043b6c0b0fa7810af/checks
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2026-04-06 14:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-03 11:34 [PATCH mptcp-next] Squash to "mptcp: better mptcp-level RTT estimator" Matthieu Baerts (NGI0)
2026-04-03 12:45 ` MPTCP CI
2026-04-06 14:18 ` Matthieu Baerts [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=950acce2-7369-4f83-9307-0131b99a3eff@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