From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>
Cc: MPTCP Upstream <mptcp@lists.linux.dev>
Subject: Re: [PATCH mptcp-next] selftests: mptcp: join: no SKIP mark for group checks
Date: Tue, 27 Jan 2026 13:25:10 +0100 [thread overview]
Message-ID: <fa22372c-1cef-4453-a6af-358db2654f3e@kernel.org> (raw)
In-Reply-To: <48222a07ad8d4d11668e293527a354640bdafec5.camel@kernel.org>
Hi Geliang,
On 27/01/2026 07:54, Geliang Tang wrote:
> Thanks for the explanation.
>
> This patch looks good to me.
Thank you for the review.
Now in our tree:
New patches for t/upstream:
- 63c83cd4d42f: selftests: mptcp: join: no SKIP mark for group checks
- Results: 7db9a30f8664..cd96e4ab92c2 (export)
Tests are now in progress:
- export:
https://github.com/multipath-tcp/mptcp_net-next/commit/0ad06206f9d3a1a2ad955b58a9425598eb9b3196/checks
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2026-01-27 12:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-11 18:09 [PATCH mptcp-next] selftests: mptcp: join: no SKIP mark for group checks Matthieu Baerts (NGI0)
2025-12-11 19:17 ` MPTCP CI
2025-12-28 3:06 ` Geliang Tang
2026-01-26 18:42 ` Matthieu Baerts
2026-01-27 6:54 ` Geliang Tang
2026-01-27 12:25 ` 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=fa22372c-1cef-4453-a6af-358db2654f3e@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