MPTCP Linux Development
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>, mptcp@lists.linux.dev
Subject: Re: [PATCH resend mptcp-net 0/4] mptcp: a few fixes
Date: Tue, 18 Aug 2026 18:26:45 +0200	[thread overview]
Message-ID: <6059ccd9-e28f-42f9-90cf-267d3d645a3f@kernel.org> (raw)
In-Reply-To: <2a74fda9614c9a11b8789a33dcda21378660534c.camel@kernel.org>

Hi Geliang,

On 18/08/2026 09:52, Geliang Tang wrote:
> Hi Matt,
> 
> On Sat, 2026-08-15 at 19:19 +0200, Matthieu Baerts wrote:
>> Hi Paolo,
>>
>> 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.
>>
>> Thank you for this series, it looks good to me:
>>
>> Reviewed-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
>>
>> I will wait for the net-next → net merge to apply them to export-net.
> 
> If you have time, could you please merge this series into the export
> branch at your earliest convenience? My ongoing series, "Reduce the
> differences between TCP and MPTCP for TLS usage", conflicts with this
> one.
If that's OK, I will wait for the Net maintainers to send their PR to
Linus, which should be done in a day or two I suppose. Is that OK?

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.


  reply	other threads:[~2026-08-18 16:26 UTC|newest]

Thread overview: 12+ 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 [this message]
2026-08-19  6:30       ` Geliang Tang

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=6059ccd9-e28f-42f9-90cf-267d3d645a3f@kernel.org \
    --to=matttbe@kernel.org \
    --cc=geliang@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