public inbox for mptcp@lists.linux.dev
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: David Ahern <dsahern@kernel.org>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
	netdev@vger.kernel.org, MPTCP Linux <mptcp@lists.linux.dev>,
	Mat Martineau <martineau@kernel.org>,
	Geliang Tang <geliang@kernel.org>
Subject: Re: [PATCH iproute2-net 0/6] mptcp: new endpoint type and info flags
Date: Tue, 2 Dec 2025 07:15:43 +0100 (GMT+01:00)	[thread overview]
Message-ID: <a92d7456-67a0-44bd-be03-99f17846a213@kernel.org> (raw)
In-Reply-To: <23baf995-080d-4457-b089-a88a317425d2@kernel.org>

Hi David,

2 Dec 2025 03:34:42 David Ahern <dsahern@kernel.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@kernel.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

  reply	other threads:[~2025-12-02  6:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-24 11:19 [PATCH iproute2-net 0/6] mptcp: new endpoint type and info flags Matthieu Baerts (NGI0)
2025-11-24 11:19 ` [PATCH iproute2-net 1/6] MAINTAINERS: add entry for mptcp Matthieu Baerts (NGI0)
2025-11-24 11:19 ` [PATCH iproute2-net 2/6] man: mptcp: fix minor typos Matthieu Baerts (NGI0)
2025-11-24 11:19 ` [PATCH iproute2-net 3/6] mptcp: add 'laminar' endpoint support Matthieu Baerts (NGI0)
2025-11-24 11:19 ` [PATCH iproute2-net 4/6] mptcp: monitor: add 'server side' info Matthieu Baerts (NGI0)
2025-11-24 11:19 ` [PATCH iproute2-net 5/6] mptcp: monitor: add 'deny join id0' info Matthieu Baerts (NGI0)
2025-11-24 11:19 ` [PATCH iproute2-net 6/6] mptcp: monitor: support 'server side' as a flag Matthieu Baerts (NGI0)
2025-12-02  2:34 ` [PATCH iproute2-net 0/6] mptcp: new endpoint type and info flags David Ahern
2025-12-02  6:15   ` Matthieu Baerts [this message]
2025-12-02 15:36     ` David Ahern

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=a92d7456-67a0-44bd-be03-99f17846a213@kernel.org \
    --to=matttbe@kernel.org \
    --cc=dsahern@kernel.org \
    --cc=geliang@kernel.org \
    --cc=martineau@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox