From: Stephen Hemminger <stephen@networkplumber.org>
To: David Ahern <dsahern@kernel.org>
Cc: roopa@nvidia.com, razor@blackwall.org, bridge@lists.linux.dev,
netdev@vger.kernel.org, liuhangbin@gmail.com,
Tobias Waldekranz <tobias@waldekranz.com>
Subject: Re: [PATCH v3 iproute2 0/4] Multiple Spanning Tree (MST) Support
Date: Fri, 5 Jul 2024 20:49:15 -0700 [thread overview]
Message-ID: <20240705204915.1e9333ae@hermes.local> (raw)
In-Reply-To: <d6e8ce6e-53f4-4f69-951e-e300477f1ebe@kernel.org>
On Fri, 5 Jul 2024 18:53:47 -0600
David Ahern <dsahern@kernel.org> wrote:
> On 7/5/24 11:31 AM, patchwork-bot+netdevbpf@kernel.org wrote:
> > Hello:
> >
> > This series was applied to iproute2/iproute2.git (main)
> > by Stephen Hemminger <stephen@networkplumber.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.
next prev parent reply other threads:[~2024-07-06 3:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 12:08 [PATCH v3 iproute2 0/4] Multiple Spanning Tree (MST) Support Tobias Waldekranz
2024-07-02 12:08 ` [PATCH v3 iproute2 1/4] ip: bridge: add support for mst_enabled Tobias Waldekranz
2024-07-02 12:08 ` [PATCH v3 iproute2 2/4] bridge: Remove duplicated textification macros Tobias Waldekranz
2024-07-02 12:08 ` [PATCH v3 iproute2 3/4] bridge: vlan: Add support for setting a VLANs MSTI Tobias Waldekranz
2024-07-02 12:08 ` [PATCH v3 iproute2 4/4] bridge: mst: Add get/set support for MST states Tobias Waldekranz
2024-07-05 17:31 ` [PATCH v3 iproute2 0/4] Multiple Spanning Tree (MST) Support patchwork-bot+netdevbpf
2024-07-06 0:53 ` David Ahern
2024-07-06 3:49 ` Stephen Hemminger [this message]
2024-07-06 15:26 ` David Ahern
2024-07-06 19:56 ` Stephen Hemminger
2024-07-07 16:16 ` David Ahern
2024-07-07 21:16 ` Stephen Hemminger
2024-07-08 22:40 ` patchwork-bot+netdevbpf
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=20240705204915.1e9333ae@hermes.local \
--to=stephen@networkplumber.org \
--cc=bridge@lists.linux.dev \
--cc=dsahern@kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.com \
--cc=tobias@waldekranz.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.