From: Matthieu Baerts <matthieu.baerts@tessares.net>
To: Geliang Tang <geliang.tang@suse.com>, mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next v20 00/10] update userspace pm mptcp_info fields part 2
Date: Tue, 20 Jun 2023 13:50:09 +0200 [thread overview]
Message-ID: <525a9a90-e55b-cef1-cb10-ff8352700a48@tessares.net> (raw)
In-Reply-To: <cover.1686900596.git.geliang.tang@suse.com>
Hi Geliang,
On 16/06/2023 09:30, Geliang Tang wrote:
> v20:
> - #1-#8, only update the commit logs with warnings reported by checkpatch.
> - #10 don't update the tests which needs to be slower than before.
Thank you for the patches!
The first 8 patches have now been applied in our tree (feat. for
net-next) with my RvB tags and the suggested modifications for patch 3/8.
New patches for t/upstream:
- 311a895fb08b: mptcp: pass addr to mptcp_pm_alloc_anno_list
- 892a2add5178: selftests: mptcp: test userspace pm out of transfer
- 34da8c8c875b: selftests: mptcp: check subflow and addr infos
- 0aadb9475af5: selftests: mptcp: set FAILING_LINKS in run_tests
- b3ec9662b408: selftests: mptcp: drop test_linkfail parameter
- 5380de466d42: selftests: mptcp: drop addr_nr_ns1/2 parameters
- fc162dadad12: selftests: mptcp: drop sflags parameter
- 75bfcf686b7e: selftests: mptcp: add pm_nl_set_endpoint helper
- Results: d937892749f1..bd3628a02b79 (export)
Tests are now in progress:
https://cirrus-ci.com/github/multipath-tcp/mptcp_net-next/export/20230620T114901
Cheers,
Matt
--
Tessares | Belgium | Hybrid Access Solutions
www.tessares.net
prev parent reply other threads:[~2023-06-20 11:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 7:30 [PATCH mptcp-next v20 00/10] update userspace pm mptcp_info fields part 2 Geliang Tang
2023-06-16 7:30 ` [PATCH mptcp-next v20 01/10] mptcp: pass addr to mptcp_pm_alloc_anno_list Geliang Tang
2023-06-16 7:30 ` [PATCH mptcp-next v20 02/10] selftests: mptcp: test userspace pm out of transfer Geliang Tang
2023-06-16 7:30 ` [PATCH mptcp-next v20 03/10] selftests: mptcp: check subflow and addr infos Geliang Tang
2023-06-19 15:01 ` Matthieu Baerts
2023-06-20 5:15 ` Geliang Tang
2023-06-16 7:30 ` [PATCH mptcp-next v20 04/10] selftests: mptcp: set FAILING_LINKS in run_tests Geliang Tang
2023-06-16 7:30 ` [PATCH mptcp-next v20 05/10] selftests: mptcp: drop test_linkfail parameter Geliang Tang
2023-06-16 7:30 ` [PATCH mptcp-next v20 06/10] selftests: mptcp: drop addr_nr_ns1/2 parameters Geliang Tang
2023-06-16 7:30 ` [PATCH mptcp-next v20 07/10] selftests: mptcp: drop sflags parameter Geliang Tang
2023-06-16 7:31 ` [PATCH mptcp-next v20 08/10] selftests: mptcp: add pm_nl_set_endpoint helper Geliang Tang
2023-06-16 7:31 ` [PATCH mptcp-next v20 09/10] selftests: mptcp: pass fastclose to sflags Geliang Tang
2023-06-19 15:04 ` Matthieu Baerts
2023-06-16 7:31 ` [PATCH mptcp-next v20 10/10] selftests: mptcp: set endpoint out of transfer Geliang Tang
2023-06-16 8:37 ` selftests: mptcp: set endpoint out of transfer: Tests Results MPTCP CI
2023-06-19 15:05 ` [PATCH mptcp-next v20 10/10] selftests: mptcp: set endpoint out of transfer Matthieu Baerts
2023-06-19 15:57 ` selftests: mptcp: set endpoint out of transfer: Tests Results MPTCP CI
2023-06-19 14:56 ` [PATCH mptcp-next v20 00/10] update userspace pm mptcp_info fields part 2 Matthieu Baerts
2023-06-20 11:50 ` 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=525a9a90-e55b-cef1-cb10-ff8352700a48@tessares.net \
--to=matthieu.baerts@tessares.net \
--cc=geliang.tang@suse.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox