From: Stephen Hemminger <stephen@networkplumber.org>
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: David Ahern <dsahern@kernel.org>,
Networking <netdev@vger.kernel.org>,
Tobias Waldekranz <tobias@waldekranz.com>
Subject: Re: [iproute2] No mst support for bridge?
Date: Thu, 13 Jun 2024 09:36:54 -0700 [thread overview]
Message-ID: <20240613093654.2d33d800@hermes.local> (raw)
In-Reply-To: <Zmsc54cVKF1wpzj7@Laptop-X1>
On Thu, 13 Jun 2024 18:23:03 +0200
Hangbin Liu <liuhangbin@gmail.com> wrote:
> Hi David,
>
> I can't recall why iproute2 doesn't have bridge mst support after
> ec7328b59176 ("net: bridge: mst: Multiple Spanning Tree (MST) mode") and
> 122c29486e1f ("net: bridge: mst: Support setting and reporting MST port states")
>
> Is there a reason that we rejected the iproute2 patch? Or Tobias didn't submit
> the patch?
>
> Thanks
> Hangbin
I never saw a patch, and searching the archives does not show it either.
Maybe never submitted or blocked by spam filter.
next prev parent reply other threads:[~2024-06-13 16:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 16:23 [iproute2] No mst support for bridge? Hangbin Liu
2024-06-13 16:36 ` Stephen Hemminger [this message]
2024-06-13 20:34 ` Tobias Waldekranz
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=20240613093654.2d33d800@hermes.local \
--to=stephen@networkplumber.org \
--cc=dsahern@kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).