From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next v5 0/2] add the id argument for set_flags
Date: Wed, 26 Jan 2022 10:56:21 +0800 [thread overview]
Message-ID: <cover.1643165468.git.geliang.tang@suse.com> (raw)
v5:
v4:
- update the output of pm_netlink.sh
v3:
- update the usage of set_flags in #1
- check more of the intermediate states with "pm_nl_ctl dump" in #2
v2:
- make standalone patches, instead of squash-to ones.
- add test cases in pm_netlink.sh, instead of mptcp_join.sh
Add the id argument for 'pm_nl_ctl set', and allow to use the port keyword
with the non-signal flags for the setting flags in 'ip mptcp endpoint
change', more commands can be used to set the address flags:
pm_nl_ctl set 10.0.2.1 flags backup port 10100
pm_nl_ctl set id 1 flags backup
ip mptcp endpoint change id 1 backup
ip mptcp endpoint change 10.0.2.1 backup port 10100
Geliang Tang (2):
selftests: mptcp: add the id argument for set_flags
selftests: mptcp: add set_flags tests in pm_netlink.sh
.../testing/selftests/net/mptcp/pm_netlink.sh | 18 ++++++
tools/testing/selftests/net/mptcp/pm_nl_ctl.c | 63 ++++++++++++-------
2 files changed, 60 insertions(+), 21 deletions(-)
--
2.31.1
next reply other threads:[~2022-01-26 2:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 2:56 Geliang Tang [this message]
2022-01-26 2:56 ` [PATCH mptcp-next v5 1/2] selftests: mptcp: add the id argument for set_flags Geliang Tang
2022-01-26 2:56 ` [PATCH mptcp-next v5 2/2] selftests: mptcp: add set_flags tests in pm_netlink.sh Geliang Tang
2022-01-26 21:45 ` [PATCH mptcp-next v5 0/2] add the id argument for set_flags Mat Martineau
2022-01-28 17:09 ` 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=cover.1643165468.git.geliang.tang@suse.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.