All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geliang Tang <geliang.tang@suse.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
	David Ahern <dsahern@kernel.org>
Cc: Geliang Tang <geliang.tang@suse.com>,
	netdev@vger.kernel.org, mptcp@lists.linux.dev
Subject: [PATCH iproute2-next v2 0/3] mptcp: add the fullmesh flag setting support
Date: Wed, 23 Feb 2022 10:59:46 +0800	[thread overview]
Message-ID: <cover.1645584573.git.geliang.tang@suse.com> (raw)

This patchset added the fullmesh flags setting, the related flags checks
and updated the usage.

v2:
 - split into three patches, each one does one thing.
 - update the commit log.

base-commit: e8fd4d4b8448c1e1dfe56b260af50c191a3f4cdd

Geliang Tang (3):
  mptcp: add fullmesh check for adding address
  mptcp: add fullmesh support for setting flags
  mptcp: add port support for setting flags

 ip/ipmptcp.c        | 28 ++++++++++++++++++++--------
 man/man8/ip-mptcp.8 | 17 ++++++++++++-----
 2 files changed, 32 insertions(+), 13 deletions(-)

-- 
2.34.1


             reply	other threads:[~2022-02-23  2:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23  2:59 Geliang Tang [this message]
2022-02-23  2:59 ` [PATCH iproute2-next v2 1/3] mptcp: add fullmesh check for adding address Geliang Tang
2022-02-23  3:08   ` Stephen Hemminger
2022-02-23  2:59 ` [PATCH iproute2-next v2 2/3] mptcp: add fullmesh support for setting flags Geliang Tang
2022-02-23  2:59 ` [PATCH iproute2-next v2 3/3] mptcp: add port " Geliang Tang
  -- strict thread matches above, loose matches on Subject: below --
2022-02-21  6:12 [PATCH iproute2-next v2 0/3] mptcp: add the fullmesh flag setting support Geliang Tang

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.1645584573.git.geliang.tang@suse.com \
    --to=geliang.tang@suse.com \
    --cc=dsahern@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    /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.