netdev - Re: [PATCH v3 iproute2 0/4] Multiple Spanning Tree (MST) Support

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <547c13c8-c3c3-495e-8ca9-d87156bfe3f5@kernel.org>
Date: Sat, 6 Jul 2024 09:26:46 -0600
From: David Ahern <dsahern@...nel.org>
To: Stephen Hemminger <stephen@...workplumber.org>
Cc: roopa@...dia.com, razor@...ckwall.org, bridge@...ts.linux.dev,
 netdev@...r.kernel.org, liuhangbin@...il.com,
 Tobias Waldekranz <tobias@...dekranz.com>
Subject: Re: [PATCH v3 iproute2 0/4] Multiple Spanning Tree (MST) Support

On 7/5/24 9:49 PM, Stephen Hemminger wrote:
> On Fri, 5 Jul 2024 18:53:47 -0600
> David Ahern <dsahern@...nel.org> wrote:
> 
>> On 7/5/24 11:31 AM, patchwork-bot+netdevbpf@...nel.org wrote:
>>> Hello:
>>>
>>> This series was applied to iproute2/iproute2.git (main)
>>> by Stephen Hemminger <stephen@...workplumber.org>:
>>>   
>>
>> Why was this merged to the main repro? As a new feature to iproute2 this
>> should be committed to next and only put in main on the next dev cycle.
> 
> Because the kernel support was already added, I prefer to not force waiting
> for code that is non-intrusive and kernel support is already present.

I have told multiple people - with you in CC - that is not how iproute2
branching works. People need to send userspace patches for iproute2 in
the same dev cycle as the kernel patches. You are now selectively
undermining that process. What is the point of -next branch then?