From: Matthieu Baerts <matttbe@kernel.org>
To: MPTCP Linux <mptcp@lists.linux.dev>
Subject: Re: [PATCH mptcp-next 0/2] selftests: mptcp: add time per subtests in TAP output (part 2)
Date: Fri, 6 Sep 2024 19:25:12 +0200 [thread overview]
Message-ID: <7ecbd01e-e902-4ac7-adef-a388a8510606@kernel.org> (raw)
In-Reply-To: <20240906-selftests-mptcp-trailing-ws-v1-0-03421b02c48e@kernel.org>
Hello,
On 06/09/2024 19:15, Matthieu Baerts (NGI0) wrote:
> After having sent the series with the same name to Netdev, Jakub
> realised the TAP parser was not properly handling the spaces around the
> directive delimiter (#).
I suggest sending these patches to netdev directly, as it was asked by
Jakub, and the modifications are simple.
New patches for t/upstream:
- c46ea800458c: selftests: mptcp: diag: remove trailing whitespace
- 7da3b70b8c1a: selftests: mptcp: connect: remove duplicated spaces in
TAP output
- Results: 9e55e13281d2..b378722dfb2e (export)
Tests are now in progress:
- export:
https://github.com/multipath-tcp/mptcp_net-next/commit/1d732d34a947c22f60161fa2bd1c0e6e9b14f56f/checks
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2024-09-06 17:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 17:15 [PATCH mptcp-next 0/2] selftests: mptcp: add time per subtests in TAP output (part 2) Matthieu Baerts (NGI0)
2024-09-06 17:15 ` [PATCH mptcp-next 1/2] selftests: mptcp: diag: remove trailing whitespace Matthieu Baerts (NGI0)
2024-09-06 17:15 ` [PATCH mptcp-next 2/2] selftests: mptcp: connect: remove duplicated spaces in TAP output Matthieu Baerts (NGI0)
2024-09-06 17:25 ` Matthieu Baerts [this message]
2024-09-06 18:14 ` [PATCH mptcp-next 0/2] selftests: mptcp: add time per subtests in TAP output (part 2) MPTCP CI
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=7ecbd01e-e902-4ac7-adef-a388a8510606@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.