netdev - Re: [PATCH iproute2-net 0/6] mptcp: new endpoint type and info flags

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <55505373-ca59-400c-8d66-2f4b73c89830@kernel.org>
Date: Tue, 2 Dec 2025 08:36:05 -0700
From: David Ahern <dsahern@...nel.org>
To: Matthieu Baerts <matttbe@...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

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.