From: Mat Martineau <martineau@kernel.org>
To: Geliang Tang <geliang@kernel.org>
Cc: mptcp@lists.linux.dev, Geliang Tang <tanggeliang@kylinos.cn>
Subject: Re: [PATCH mptcp-next v3 0/2] fixes for "map v4 address to v6"
Date: Tue, 13 Feb 2024 17:44:50 -0800 (PST) [thread overview]
Message-ID: <59fce9d5-366e-1231-6472-41f35a1da5f8@kernel.org> (raw)
In-Reply-To: <cover.1707270765.git.tanggeliang@kylinos.cn>
On Wed, 7 Feb 2024, Geliang Tang wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
>
> v3:
> - add a new argument addr for mptcp_lib_evts_get_info, instead of
> a new helper mptcp_lib_evts_get_info_with_addr
v3 looks good to me, thanks Geliang.
Reviewed-by: Mat Martineau <martineau@kernel.org>
>
> v2:
> - update selftests as Mat suggested.
>
> Geliang Tang (2):
> mptcp: map v4 address to v6 when destroying subflow
> selftests: mptcp: rm subflow with v4/v4mapped addr
>
> net/mptcp/pm_userspace.c | 10 +++++++
> .../testing/selftests/net/mptcp/mptcp_join.sh | 28 +++++++++++--------
> .../testing/selftests/net/mptcp/mptcp_lib.sh | 7 +++--
> 3 files changed, 31 insertions(+), 14 deletions(-)
>
> --
> 2.40.1
>
>
>
next prev parent reply other threads:[~2024-02-14 1:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 1:55 [PATCH mptcp-next v3 0/2] fixes for "map v4 address to v6" Geliang Tang
2024-02-07 1:55 ` [PATCH mptcp-next v3 1/2] mptcp: map v4 address to v6 when destroying subflow Geliang Tang
2024-02-07 1:55 ` [PATCH mptcp-next v3 2/2] selftests: mptcp: rm subflow with v4/v4mapped addr Geliang Tang
2024-02-07 2:49 ` selftests: mptcp: rm subflow with v4/v4mapped addr: Tests Results MPTCP CI
2024-02-07 3:11 ` MPTCP CI
2024-02-14 2:36 ` MPTCP CI
2024-02-14 2:55 ` MPTCP CI
2024-02-14 10:18 ` [PATCH mptcp-next v3 2/2] selftests: mptcp: rm subflow with v4/v4mapped addr Matthieu Baerts
2024-02-14 11:47 ` Geliang Tang
2024-02-14 1:44 ` Mat Martineau [this message]
2024-02-14 10:28 ` [PATCH mptcp-next v3 0/2] fixes for "map v4 address to v6" Matthieu Baerts
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=59fce9d5-366e-1231-6472-41f35a1da5f8@kernel.org \
--to=martineau@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