From: David Ahern <dsahern@kernel.org>
To: Matthieu Baerts <matttbe@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 08:36:05 -0700 [thread overview]
Message-ID: <55505373-ca59-400c-8d66-2f4b73c89830@kernel.org> (raw)
In-Reply-To: <a92d7456-67a0-44bd-be03-99f17846a213@kernel.org>
On 12/1/25 11:15 PM, Matthieu Baerts wrote:
> 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]?
>
iproute2-main is the bug fix and release tree. It is not for features.
iproute2-next is the development and feature tree. If features are to
sync with kernel side merges, then the patches need to show up at the
same time.
prev parent reply other threads:[~2025-12-02 15:36 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
2025-12-02 15:36 ` David Ahern [this message]
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=55505373-ca59-400c-8d66-2f4b73c89830@kernel.org \
--to=dsahern@kernel.org \
--cc=geliang@kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@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