From: Paolo Abeni <pabeni@redhat.com>
To: mptcp@lists.linux.dev
Subject: [PATCH resend mptcp-net 0/4] mptcp: a few fixes
Date: Fri, 14 Aug 2026 15:38:19 +0200 [thread overview]
Message-ID: <cover.1786713351.git.pabeni@redhat.com> (raw)
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.
---
resent to hopefully trigger sashiko
Paolo Abeni (4):
mptcp: being below memory limit is a likely() condition
mptcp: avoid pruning for OoW data
mptcp: remove unneeded READ_ONCE() annotation
mptcp: do not reschedule the RTX timer for fallback sockets
net/mptcp/options.c | 4 ++--
net/mptcp/protocol.c | 29 +++++++++++++++++------------
net/mptcp/protocol.h | 1 +
3 files changed, 20 insertions(+), 14 deletions(-)
--
2.55.0
next reply other threads:[~2026-08-14 13:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 13:38 Paolo Abeni [this message]
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
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=cover.1786713351.git.pabeni@redhat.com \
--to=pabeni@redhat.com \
--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 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.