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 v4 0/4] add helpers and vars in mptcp_lib.sh, part 2
Date: Thu, 22 Feb 2024 12:39:21 +0100 [thread overview]
Message-ID: <6b3f316f-c0b6-493f-a73d-b607c819f8de@kernel.org> (raw)
In-Reply-To: <3c77c0a0-3150-4421-b2ed-b064393c49b8@kernel.org>
Hi Geliang,
On 22/02/2024 11:30 am, Matthieu Baerts wrote:
> Hi Geliang,
>
> On 22/02/2024 4:40 am, Geliang Tang wrote:
>> From: Geliang Tang <tanggeliang@kylinos.cn>
>>
>> v4:
>> - address Matt's comments in v3 except
>> - keep #1, #3 as separate patches, not squash them into #2, to keep #2
>> clean.
>
> Thank you for the v4, it looks better to me!
>
> Reviewed-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
>
> I have just one comment for patch 2/4, but it is fine, I think. (I will
> also add {} around the new 'netns' variable in mptcp_lib.sh when
> applying the patch.)
I just applied the new patches with the suggested modifications.
New patches for t/upstream:
- b19e35a9c85b: selftests: mptcp: add local variables rndh
- 1e458efc9900: selftests: mptcp: add mptcp_lib_ns_init/exit helpers
- dcb564917e5b: selftests: mptcp: more operations in ns_init/exit
- d734b17e00dd: selftests: mptcp: add mptcp_lib_events helper
- Results: a542d2d60003..80a8f9458231 (export)
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2024-02-22 11:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 3:40 [PATCH mptcp-next v4 0/4] add helpers and vars in mptcp_lib.sh, part 2 Geliang Tang
2024-02-22 3:40 ` [PATCH mptcp-next v4 1/4] selftests: mptcp: add local variables rndh Geliang Tang
2024-02-22 3:40 ` [PATCH mptcp-next v4 2/4] selftests: mptcp: add mptcp_lib_ns_init/exit helpers Geliang Tang
2024-02-22 10:34 ` Matthieu Baerts
2024-02-22 3:40 ` [PATCH mptcp-next v4 3/4] selftests: mptcp: more operations in ns_init/exit Geliang Tang
2024-02-22 3:40 ` [PATCH mptcp-next v4 4/4] selftests: mptcp: add mptcp_lib_events helper Geliang Tang
2024-02-22 4:31 ` selftests: mptcp: add mptcp_lib_events helper: Tests Results MPTCP CI
2024-02-22 11:07 ` [PATCH mptcp-next v4 4/4] selftests: mptcp: add mptcp_lib_events helper Matthieu Baerts
2024-02-22 11:15 ` Matthieu Baerts
2024-02-22 10:30 ` [PATCH mptcp-next v4 0/4] add helpers and vars in mptcp_lib.sh, part 2 Matthieu Baerts
2024-02-22 11:39 ` 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=6b3f316f-c0b6-493f-a73d-b607c819f8de@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