From: David Ahern <dsahern@gmail.com>
To: Davide Caratti <dcaratti@redhat.com>,
netdev@vger.kernel.org, David Ahern <dsahern@gmail.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Andrea Claudi <aclaudi@redhat.com>
Cc: Matthieu Baerts <matthieu.baerts@tessares.net>
Subject: Re: [PATCH iproute2-next] mptcp: add support for changing the backup flag
Date: Mon, 13 Dec 2021 20:25:40 -0700 [thread overview]
Message-ID: <43124a32-b509-bbbc-ea3f-38aa4c656b86@gmail.com> (raw)
In-Reply-To: <cb2ddffb2211d6fdde7a8bf81879a3a83c620f00.1639039948.git.dcaratti@redhat.com>
On 12/9/21 2:10 AM, Davide Caratti wrote:
> Linux supports 'MPTCP_PM_CMD_SET_FLAGS' since v5.12, and this control has
> recently been extended to allow setting flags for a given endpoint id.
> Although there is no use for changing 'signal' or 'subflow' flags, it can
> be helpful to set/clear the backup bit on existing endpoints: add the 'ip
> mptcp endpoint change <...>' command for this purpose.
>
> Link: https://github.com/multipath-tcp/mptcp_net-next/issues/158
> Acked-by: Matthieu Baerts <matthieu.baerts@tessares.net>
> Signed-off-by: Davide Caratti <dcaratti@redhat.com>
> ---
> ip/ipmptcp.c | 20 ++++++++++++++++----
> man/man8/ip-mptcp.8 | 14 ++++++++++++++
> 2 files changed, 30 insertions(+), 4 deletions(-)
>
does not apply to iproute2-next; please rebase.
next prev parent reply other threads:[~2021-12-14 3:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 9:10 [PATCH iproute2-next] mptcp: add support for changing the backup flag Davide Caratti
2021-12-14 3:25 ` David Ahern [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-12-03 15:01 Davide Caratti
2021-12-08 1:59 ` Mat Martineau
2021-12-08 10:23 ` Matthieu Baerts
2021-12-08 23:19 ` Mat Martineau
2021-11-26 9:38 Davide Caratti
2021-11-26 17:06 ` 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=43124a32-b509-bbbc-ea3f-38aa4c656b86@gmail.com \
--to=dsahern@gmail.com \
--cc=aclaudi@redhat.com \
--cc=dcaratti@redhat.com \
--cc=matthieu.baerts@tessares.net \
--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.