All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geliang Tang <geliang.tang@suse.com>
To: Mat Martineau <mathew.j.martineau@linux.intel.com>
Cc: Matthieu Baerts <matthieu.baerts@tessares.net>, mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next v2 00/10] set flags and selftests
Date: Thu, 20 Jan 2022 18:20:56 +0800	[thread overview]
Message-ID: <20220120102056.GA2930@bogon> (raw)
In-Reply-To: <c135c322-e71f-f525-ba83-ea53691e65f@linux.intel.com>

On Wed, Jan 19, 2022 at 05:01:53PM -0800, Mat Martineau wrote:
> On Sun, 16 Jan 2022, Geliang Tang wrote:
> 
> > v2:
> > - use a mask of changed flags as Mat suggested.
> > - squash patch 8 and patch 9 in v1 into one.
> > 
> 
> v2 looks ready for the export branch, thanks Geliang.
> 
> Reviewed-by: Mat Martineau <mathew.j.martineau@linux.intel.com>

Please add Paolo's Acked-by tag for the first three patches.

Thanks,
-Geliang

> 
> 
> > Geliang Tang (10):
> >  mptcp: set fullmesh flag in pm_netlink
> >  selftests: mptcp: set fullmesh flag in pm_nl_ctl
> >  selftests: mptcp: add fullmesh setting tests
> >  mptcp: allow to use port and non-signal in set_flags
> >  selftests: mptcp: add the port argument for set_flags
> >  selftests: mptcp: add backup with port testcase
> >  selftests: mptcp: add ip mptcp wrappers
> >  selftests: mptcp: add wrapper for showing addrs
> >  selftests: mptcp: add wrapper for setting flags
> >  selftests: mptcp: set ip_mptcp in command line
> > 
> > net/mptcp/pm_netlink.c                        |  50 +-
> > .../testing/selftests/net/mptcp/mptcp_join.sh | 936 +++++++++++-------
> > tools/testing/selftests/net/mptcp/pm_nl_ctl.c |  19 +-
> > 3 files changed, 616 insertions(+), 389 deletions(-)
> > 
> 
> --
> Mat Martineau
> Intel
> 


  reply	other threads:[~2022-01-20 10:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-16  8:17 [PATCH mptcp-next v2 00/10] set flags and selftests Geliang Tang
2022-01-16  8:17 ` [PATCH mptcp-next v2 01/10] mptcp: set fullmesh flag in pm_netlink Geliang Tang
2022-01-16  8:17 ` [PATCH mptcp-next v2 02/10] selftests: mptcp: set fullmesh flag in pm_nl_ctl Geliang Tang
2022-01-16  8:17 ` [PATCH mptcp-next v2 03/10] selftests: mptcp: add fullmesh setting tests Geliang Tang
2022-01-16  8:17 ` [PATCH mptcp-next v2 04/10] mptcp: allow to use port and non-signal in set_flags Geliang Tang
2022-01-16  8:17 ` [PATCH mptcp-next v2 05/10] selftests: mptcp: add the port argument for set_flags Geliang Tang
2022-01-16  8:17 ` [PATCH mptcp-next v2 06/10] selftests: mptcp: add backup with port testcase Geliang Tang
2022-01-16  8:17 ` [PATCH mptcp-next v2 07/10] selftests: mptcp: add ip mptcp wrappers Geliang Tang
2022-01-16  8:17 ` [PATCH mptcp-next v2 08/10] selftests: mptcp: add wrapper for showing addrs Geliang Tang
2022-01-16  8:17 ` [PATCH mptcp-next v2 09/10] selftests: mptcp: add wrapper for setting flags Geliang Tang
2022-01-16  8:17 ` [PATCH mptcp-next v2 10/10] selftests: mptcp: set ip_mptcp in command line Geliang Tang
2022-01-20  1:01 ` [PATCH mptcp-next v2 00/10] set flags and selftests Mat Martineau
2022-01-20 10:20   ` Geliang Tang [this message]
2022-01-20 14:47     ` Matthieu Baerts
2022-01-20 15:04 ` 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=20220120102056.GA2930@bogon \
    --to=geliang.tang@suse.com \
    --cc=mathew.j.martineau@linux.intel.com \
    --cc=matthieu.baerts@tessares.net \
    --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.