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 v3 0/2] fixes for "map v4 address to v6"
Date: Wed, 14 Feb 2024 11:28:09 +0100 [thread overview]
Message-ID: <4b845333-167e-4992-83b3-46001aefc8d0@kernel.org> (raw)
In-Reply-To: <cover.1707270765.git.tanggeliang@kylinos.cn>
Hi Geliang, Mat,
On 07/02/2024 02:55, 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
>
> 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
Thank you for the patches and the reviews!
Now in our tree (fixes for -net), with Mat and my RvB tags, and the
modification I mentioned in patch 2/2.
New patches for t/upstream-net and t/upstream:
- cc6b8f6f3d24: mptcp: map v4 address to v6 when destroying subflow
- bbc429327d25: selftests: mptcp: rm subflow with v4/v4mapped addr
- Results: 0675fccde951..abfdc616f556 (export-net)
- Results: f63a9c1dbbaa..ce1856db2249 (export)
Tests are now in progress:
https://cirrus-ci.com/github/multipath-tcp/mptcp_net-next/export-net/20240214T102432
https://cirrus-ci.com/github/multipath-tcp/mptcp_net-next/export/20240214T102432
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2024-02-14 10:28 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 ` [PATCH mptcp-next v3 0/2] fixes for "map v4 address to v6" Mat Martineau
2024-02-14 10:28 ` 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=4b845333-167e-4992-83b3-46001aefc8d0@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