From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>, mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: Re: [PATCH mptcp-next 0/2] two tc related patches
Date: Wed, 13 Mar 2024 12:03:16 +0100 [thread overview]
Message-ID: <6285e266-7d5a-4475-bd36-223be1a2c61d@kernel.org> (raw)
In-Reply-To: <1c646579-bfb5-442c-82df-e79d2bff6ca1@kernel.org>
Hi Geliang,
On 13/03/2024 11:15, Matthieu Baerts wrote:
> Hi Geliang,
>
> On 13/03/2024 04:13, Geliang Tang wrote:
>> From: Geliang Tang <tanggeliang@kylinos.cn>
>>
>> Two tc related patches.
>>
>> Geliang Tang (2):
>> selftests: mptcp: add tc check for check_tools
>> selftests: mptcp: add ms units for tc-netem delay
>
> Thank you, it looks good to me:
>
> Reviewed-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
Now in our tree (feat. for next):
New patches for t/upstream:
- 4daabed4354a: selftests: mptcp: add tc check for check_tools
- 3b184258a310: selftests: mptcp: add ms units for tc-netem delay
- Results: 02195e22026a..e2c5d9481519 (export)
Tests are now in progress:
- export:
https://github.com/multipath-tcp/mptcp_net-next/commit/5f3aa05a0186bfbf6f4d4feeb99657c756a6f456/checks
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2024-03-13 11:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 3:13 [PATCH mptcp-next 0/2] two tc related patches Geliang Tang
2024-03-13 3:13 ` [PATCH mptcp-next 1/2] selftests: mptcp: add tc check for check_tools Geliang Tang
2024-03-13 3:13 ` [PATCH mptcp-next 2/2] selftests: mptcp: add ms units for tc-netem delay Geliang Tang
2024-03-13 4:11 ` [mptcp-next,0/2] two tc related patches MPTCP CI
2024-03-13 10:15 ` [PATCH mptcp-next 0/2] " Matthieu Baerts
2024-03-13 11:03 ` 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=6285e266-7d5a-4475-bd36-223be1a2c61d@kernel.org \
--to=matttbe@kernel.org \
--cc=geliang@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=tanggeliang@kylinos.cn \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).