From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Geliang Tang <geliang.tang@suse.com>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH iproute2-next 0/3] more patches from pm_nl_ctl
Date: Fri, 7 Jan 2022 16:11:43 -0800 (PST) [thread overview]
Message-ID: <8de28feb-42ef-76d6-663c-32596eba1bc@linux.intel.com> (raw)
In-Reply-To: <cover.1641289518.git.geliang.tang@suse.com>
On Tue, 4 Jan 2022, Geliang Tang wrote:
> This patched added id 0 address deleting, fullmesh flag and backup setting
> from pm_nl_ctl. With these patches, we can replace all pm_nl_ctl in the
> selftests with 'ip mptcp' command.
>
> Geliang Tang (3):
> mptcp: add id check for deleting address
> mptcp: add the addr flag fullmesh
> mptcp: add the backup flag setting
>
> include/uapi/linux/mptcp.h | 2 ++
> ip/ipmptcp.c | 31 +++++++++++++++++++++++++------
> 2 files changed, 27 insertions(+), 6 deletions(-)
>
> --
> 2.31.1
Hi Geliang -
I found that this doesn't apply to
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git, but it
does apply to iproute2.git
If you check iproute2-next, there's already a patch in there from Paolo
that adds the fullmesh flag.
Can you rebase the other two patches on iproute2-next for v2?
Thanks,
--
Mat Martineau
Intel
next prev parent reply other threads:[~2022-01-08 0:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 9:58 [PATCH iproute2-next 0/3] more patches from pm_nl_ctl Geliang Tang
2022-01-04 9:58 ` [PATCH RESEND iproute2-next 1/3] mptcp: add id check for deleting address Geliang Tang
2022-01-08 0:18 ` Mat Martineau
2022-01-04 9:58 ` [PATCH iproute2-next 2/3] mptcp: add the addr flag fullmesh Geliang Tang
2022-01-04 9:58 ` [PATCH iproute2-next 3/3] mptcp: add the backup flag setting Geliang Tang
2022-01-08 0:36 ` Mat Martineau
2022-01-08 0:11 ` Mat Martineau [this message]
2022-01-10 6:46 ` [PATCH iproute2-next 0/3] more patches from pm_nl_ctl 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=8de28feb-42ef-76d6-663c-32596eba1bc@linux.intel.com \
--to=mathew.j.martineau@linux.intel.com \
--cc=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.