From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang.tang@linux.dev>, mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: Re: [PATCH mptcp-next v17 0/9] userspace pm remove id 0 subflow & address
Date: Mon, 23 Oct 2023 01:06:42 +0200 [thread overview]
Message-ID: <de18b56a-4a05-4838-b9ca-081b00f7a225@kernel.org> (raw)
In-Reply-To: <cover.1697511436.git.geliang.tang@suse.com>
Hi Geliang,
On 17/10/2023 05:00, Geliang Tang wrote:
> From: Geliang Tang <geliang.tang@suse.com>
>
> v17:
> - include "fix userspace pm CI failures" series.
> - update __mptcp_has_initial_subflow as Paolo suggested.
> - update chk_subflows_total.
> - update selftests.
Thank you for the new version, it looks good to me!
Reviewed-by: Matthieu Baerts <matttbe@kernel.org>
Now in our tree: a part in 'fixes for -net' and the rest in 'features
for net-next' and this has caused conflicts, please see below:
New patches for t/upstream-net and t/upstream:
- 20c92e1b1473: selftests: mptcp: run userspace pm tests slower
- 54b8c59e976f: selftests: mptcp: fix wait_rm_addr/sf parameters
- a9f72db763e0: mptcp: userspace pm send RM_ADDR for ID 0
- Note that I renamed the new helper to keep the 'mptcp_userspace_pm_'
prefix we can find in other helpers in this file.
- Results: 9a34fc4dbad6..a1d8e0942055 (export-net)
Conflicts:
- 9f7653e25504: conflict in
t/net-mptcp-rename-netlink-handlers-to-mptcp_pm_nl_-blah-_-doit-dumpit
- 1dae6c24941f: conflict in t/mptcp-define-more-local-variables-sk
- bff6a9fde262: conflict in
t/selftests-mptcp-update-userspace-pm-test-helpers
- Results: 65682b5b41eb..554ef3499597 (export)
Squash-to patches:
- 964ed0906f76: "squashed" patch 3/9 in "selftests: mptcp: userspace pm
create id 0 subflow"
- 6a9ab12adf72: "squashed" patch 4/9 in "mptcp: add
mptcpi_subflows_total counter"
- a65a15f44388: "squashed" patch 5/9 in "selftests: mptcp: add
chk_subflows_total helper"
- e5424462cd82: tg:msg: update after the recent squash-to patch
- Results: 554ef3499597..7592debc8c8b (export)
New patches for t/upstream:
- 492717f096ae: mptcp: userspace pm rename remove_err to out
- 702694cb477d: selftests: mptcp: userspace pm send RM_ADDR for ID 0
- Results: 7592debc8c8b..1b6c8d99ae9c (export)
Tests are now in progress:
https://cirrus-ci.com/github/multipath-tcp/mptcp_net-next/export-net/20231022T222301
https://cirrus-ci.com/github/multipath-tcp/mptcp_net-next/export/20231022T230418
Cheers,
Mat
next prev parent reply other threads:[~2023-10-22 23:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 3:00 [PATCH mptcp-next v17 0/9] userspace pm remove id 0 subflow & address Geliang Tang
2023-10-17 3:00 ` [PATCH mptcp-next v17 1/9] selftests: mptcp: run userspace pm tests slower Geliang Tang
2023-10-17 3:00 ` [PATCH mptcp-next v17 2/9] selftests: mptcp: fix wait_rm_addr/sf parameters Geliang Tang
2023-10-17 3:00 ` [PATCH mptcp-next v17 3/9] Squash to "selftests: mptcp: userspace pm create id 0 subflow" Geliang Tang
2023-10-17 3:00 ` [PATCH mptcp-next v17 4/9] Squash to "mptcp: add mptcpi_subflows_total counter" Geliang Tang
2023-10-17 3:00 ` [PATCH mptcp-next v17 5/9] Squash to "selftests: mptcp: add chk_subflows_total helper" Geliang Tang
2023-10-17 3:00 ` [PATCH mptcp-next v17 6/9] selftests: mptcp: userspace pm remove initial subflow Geliang Tang
2023-10-17 3:00 ` [PATCH mptcp-next v17 7/9] mptcp: userspace pm send RM_ADDR for ID 0 Geliang Tang
2023-10-17 3:00 ` [PATCH mptcp-next v17 8/9] mptcp: userspace pm rename remove_err to out Geliang Tang
2023-10-17 3:00 ` [PATCH mptcp-next v17 9/9] selftests: mptcp: userspace pm send RM_ADDR for ID 0 Geliang Tang
2023-10-17 4:08 ` selftests: mptcp: userspace pm send RM_ADDR for ID 0: Tests Results MPTCP CI
2023-10-22 23:06 ` Matthieu Baerts [this message]
2023-10-22 23:16 ` [PATCH mptcp-next v17 0/9] userspace pm remove id 0 subflow & address 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=de18b56a-4a05-4838-b9ca-081b00f7a225@kernel.org \
--to=matttbe@kernel.org \
--cc=geliang.tang@linux.dev \
--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