From: Matthieu Baerts <matttbe@kernel.org>
To: T S RAMESHKUMAR <rameshsv06@gmail.com>
Cc: MPTCP Linux <mptcp@lists.linux.dev>,
Petar Sakic <petar.sakic@ink.fish>,
T S Rameshkumar <rameshkumar.t@phytecembedded.in>
Subject: Re: [PATCH mptcp-net v2] mptcp: push queued data on passive TFO subflows becoming established
Date: Tue, 27 Oct 2026 11:48:41 +0100 [thread overview]
Message-ID: <cee29410-ef2b-408e-8311-866b878da4f9@kernel.org> (raw)
In-Reply-To: <CADRhS2to+Z-ZztOpfYhum5z4jXkUHFhnQL3+nVBJHJxe3NZjZw@mail.gmail.com>
Hi T S,
On 22/10/2026 04:29, T S RAMESHKUMAR wrote:
> Yes, I am working on it.
>
> I planned that the fixes that the commit has been made on the Friday 22
> Oct 2026
I'm sorry for this reminder, but everything is still OK on your side?
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2026-10-27 10:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 11:10 [PATCH mptcp-net v2] mptcp: push queued data on passive TFO subflows becoming established T S Rameshkumar
2026-10-12 12:24 ` MPTCP CI
2026-10-14 0:11 ` netdev-bot+sashiko
2026-10-14 8:28 ` Matthieu Baerts
2026-10-21 17:56 ` Matthieu Baerts
[not found] ` <CADRhS2to+Z-ZztOpfYhum5z4jXkUHFhnQL3+nVBJHJxe3NZjZw@mail.gmail.com>
2026-10-27 10:48 ` 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=cee29410-ef2b-408e-8311-866b878da4f9@kernel.org \
--to=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=petar.sakic@ink.fish \
--cc=rameshkumar.t@phytecembedded.in \
--cc=rameshsv06@gmail.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