All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matthieu.baerts at tessares.net>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [MPTCP][PATCH v3 mptcp-next 0/6] MP_PRIO support
Date: Wed, 16 Dec 2020 23:00:38 +0100	[thread overview]
Message-ID: <4a678a3e-8616-c9be-6072-10f5cac5fd53@tessares.net> (raw)
In-Reply-To: cover.1607501232.git.geliangtang@gmail.com

[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]

Hi Geliang, Mat,

On 09/12/2020 09:15, Geliang Tang wrote:
> v3:
>   - drop the MPTCP_PM_ADDR_FLAG_NOBACKUP flag
> 
> v2:
>   - add set_flags command
> 
> v1:
>   - add MP_PRIO PM netlink support

Thank you for the patches and the reviews!

- a56be1da1447: mptcp: add the outgoing MP_PRIO support 
 
 

- 661b20bcc670: mptcp: add the incoming MP_PRIO support 
 
 

- ef8d4135a450: mptcp: add set_flags command in PM netlink 
 
 

- bda492f95f00: selftests: mptcp: add set_flags command in pm_nl_ctl 
 
 

- cdd087e12b2f: mptcp: add the mibs for MP_PRIO 
 
 

- 6a9e7c4c68db: selftests: mptcp: add the MP_PRIO testcases

- 5b9a80798bf4: "squashed" in "mptcp: add the outgoing MP_PRIO support"

Tests + export have been queued!

> Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/51

Thanks for the link!

Do not forget IPRoute2 patches ;-)
(and ideally packetdrill tests :) )

Cheers,
Matt
-- 
Tessares | Belgium | Hybrid Access Solutions
www.tessares.net

             reply	other threads:[~2020-12-16 22:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-16 22:00 Matthieu Baerts [this message]
2020-12-17  8:02 [MPTCP] Re: [MPTCP][PATCH v3 mptcp-next 0/6] MP_PRIO support 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=4a678a3e-8616-c9be-6072-10f5cac5fd53@tessares.net \
    --to=unknown@example.com \
    /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.