[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a92d7456-67a0-44bd-be03-99f17846a213@kernel.org>
Date: Tue, 2 Dec 2025 07:15:43 +0100 (GMT+01:00)
From: Matthieu Baerts <matttbe@...nel.org>
To: David Ahern <dsahern@...nel.org>
Cc: Stephen Hemminger <stephen@...workplumber.org>, netdev@...r.kernel.org,
MPTCP Linux <mptcp@...ts.linux.dev>,
Mat Martineau <martineau@...nel.org>,
Geliang Tang <geliang@...nel.org>
Subject: Re: [PATCH iproute2-net 0/6] mptcp: new endpoint type and info
flags
Hi David,
2 Dec 2025 03:34:42 David Ahern <dsahern@...nel.org>:
> On 11/24/25 4:19 AM, Matthieu Baerts (NGI0) wrote:
>> Here are some patches related to MPTCP, mainly to control features that
>> will be in the future v6.18.
>>
>> - Patch 1: add an entry in the MAINTAINERS file for MPTCP.
>>
>> - Patch 2: fix two minor typos in the man page.
>>
>> - Patch 3: add laminar endpoint support.
>>
>> - Patches 4-6: display missing attributes & flags in 'ip mptcp monitor'.
>>
>> Signed-off-by: Matthieu Baerts (NGI0) <matttbe@...nel.org>
>> ---
>> Matthieu Baerts (NGI0) (6):
>> MAINTAINERS: add entry for mptcp
>> man: mptcp: fix minor typos
>> mptcp: add 'laminar' endpoint support
>> mptcp: monitor: add 'server side' info
>> mptcp: monitor: add 'deny join id0' info
>> mptcp: monitor: support 'server side' as a flag
>>
>> MAINTAINERS | 7 +++++++
>> ip/ipmptcp.c | 20 +++++++++++++++++---
>> man/man8/ip-mptcp.8 | 20 ++++++++++++++++++--
>> misc/ss.c | 2 ++
>> 4 files changed, 44 insertions(+), 5 deletions(-)
>> ---
>> base-commit: 2a82227f984b3f97354e4a490d3f172eedf07f63
>> change-id: 20251124-iproute-mptcp-laminar-2973adec2860
>>
>> Best regards,
>
> applied to iproute2-next.
Thank you!
> Patches should always be against top of tree - no assumptions. I had to
> fixup the first patch of this set which puts work on me.
I'm sorry about that!
These patches were on top of iproute2.git (not next) because they were
controlling features available in v6.18 (or older), but not only in net-next.
Should I maybe next time not prefix such patches with [iproute2-net] but
only [iproute2]?
Cheers,
Matt
Powered by blists - more mailing lists