All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next v11 0/4] userspace pm remove id 0 subflow & address
Date: Sun,  8 Oct 2023 18:27:06 +0800	[thread overview]
Message-ID: <cover.1696760702.git.geliang.tang@suse.com> (raw)

v11:
 - avoid sending RSTs.
 - rename 'id 0 subflow' to 'inital subflow'.

Geliang Tang (4):
  mptcp: set next subflow to msk->first
  selftests: mptcp: userspace pm remove initial subflow
  mptcp: userspace pm remove id 0 address
  selftests: mptcp: userspace pm remove id 0 address

 net/mptcp/pm_userspace.c                      | 36 +++++++++++++++
 net/mptcp/protocol.c                          | 18 ++++++--
 .../testing/selftests/net/mptcp/mptcp_join.sh | 44 +++++++++++++++++++
 3 files changed, 95 insertions(+), 3 deletions(-)

-- 
2.35.3


             reply	other threads:[~2023-10-08 10:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-08 10:27 Geliang Tang [this message]
2023-10-08 10:27 ` [PATCH mptcp-next v11 1/4] mptcp: set next subflow to msk->first Geliang Tang
2023-10-08 11:11   ` Matthieu Baerts
2023-10-08 12:33     ` Geliang Tang
2023-10-08 14:05       ` Matthieu Baerts
2023-10-10  6:04         ` Geliang Tang
2023-10-10 12:28           ` Matthieu Baerts
2023-10-08 10:27 ` [PATCH mptcp-next v11 2/4] selftests: mptcp: userspace pm remove initial subflow Geliang Tang
2023-10-08 11:13   ` Matthieu Baerts
2023-10-08 11:22   ` Matthieu Baerts
2023-10-08 10:27 ` [PATCH mptcp-next v11 3/4] mptcp: userspace pm remove id 0 address Geliang Tang
2023-10-08 11:19   ` Matthieu Baerts
2023-10-08 10:27 ` [PATCH mptcp-next v11 4/4] selftests: " Geliang Tang
2023-10-08 11:25   ` Matthieu Baerts
2023-10-08 12:20   ` selftests: mptcp: userspace pm remove id 0 address: Tests Results MPTCP CI

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.1696760702.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.