From: Matthieu Baerts <matttbe@kernel.org>
To: MPTCP Linux <mptcp@lists.linux.dev>
Subject: [blog] Summer update and MPTCP features in Linux v6.18
Date: Wed, 5 Nov 2025 16:21:56 +0100 [thread overview]
Message-ID: <eb97d790-a79c-46a1-a8a9-e590f3e160b6@kernel.org> (raw)
Hello,
Just in case you are not tracking the RSS feed [1], or the Fediverse
account [2], and with a bit of delay, a new blog post about MPTCP, the
recent updates and new features that will be in v6.18 is available there:
https://blog.mptcp.dev/2025/10/16/v6.18-with-many-features.html
[1] https://blog.mptcp.dev/feed.xml
[2] https://social.kernel.org/mptcp
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
reply other threads:[~2025-11-05 15:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=eb97d790-a79c-46a1-a8a9-e590f3e160b6@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