From: Matthieu Baerts <matttbe@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>, Geliang Tang <geliang@kernel.org>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH resend mptcp-net 0/4] mptcp: a few fixes
Date: Fri, 21 Aug 2026 08:42:15 +0200 [thread overview]
Message-ID: <54694029-fa40-4596-8fff-87939d982bbe@kernel.org> (raw)
In-Reply-To: <cover.1786713351.git.pabeni@redhat.com>
Hi Paolo, Geliang,
On 14/08/2026 15:38, Paolo Abeni wrote:
> This is mostly a follow-up to the recent OoO queue pruning series.
> Explicitly targeting net as we have already a lot of patches pending for
> net-next, and no need to rush IMHO.
>
> First 2 patches addresses explicit comments from sashiko, 3rd one is a
> somewhat unrelated cleanup I stumbled upon while implementing patch 4.
>
> The last patch fixes another thing implided by sashiko while reviewing
> the mentioned series.
Now in our tree:
New patches for t/upstream-net and t/upstream:
- 6280287c0ef2: mptcp: being below memory limit is a likely() condition
- e66f97348c99: mptcp: avoid pruning for OoW data
- cdd6976ab76f: mptcp: remove unneeded READ_ONCE() annotation
- 285d84ee4b60: mptcp: do not reschedule the RTX timer for fallback sockets
- Results: 6bb246941708..70d6bffa3696 (export-net)
- Results: 2f5abecdd265..0afd98c500bf (export)
Tests are now in progress:
- export-net:
https://github.com/multipath-tcp/mptcp_net-next/commit/71a020c17359779f858419627d7933171dafee9a/checks
- export:
https://github.com/multipath-tcp/mptcp_net-next/commit/8ff26825a673fb98ff86413940a0254088cf0bd3/checks
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2026-08-21 6:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 13:38 [PATCH resend mptcp-net 0/4] mptcp: a few fixes Paolo Abeni
2026-08-14 13:38 ` [PATCH resend mptcp-net 1/4] mptcp: being below memory limit is a likely() condition Paolo Abeni
2026-08-14 13:38 ` [PATCH resend mptcp-net 2/4] mptcp: avoid pruning for OoW data Paolo Abeni
2026-08-14 13:38 ` [PATCH resend mptcp-net 3/4] mptcp: remove unneeded READ_ONCE() annotation Paolo Abeni
2026-08-14 13:38 ` [PATCH resend mptcp-net 4/4] mptcp: do not reschedule the RTX timer for fallback sockets Paolo Abeni
2026-08-14 14:03 ` sashiko-bot
2026-08-14 16:33 ` Paolo Abeni
2026-08-14 14:59 ` [PATCH resend mptcp-net 0/4] mptcp: a few fixes MPTCP CI
2026-08-15 17:19 ` Matthieu Baerts
2026-08-18 7:52 ` Geliang Tang
2026-08-18 16:26 ` Matthieu Baerts
2026-08-19 6:30 ` Geliang Tang
2026-08-21 6:42 ` 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=54694029-fa40-4596-8fff-87939d982bbe@kernel.org \
--to=matttbe@kernel.org \
--cc=geliang@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=pabeni@redhat.com \
/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