From: "Hasenbosch, Samuel J" <Samuel.J.Hasenbosch@boeing.com>
To: "bugs.a.b@free.fr" <bugs.a.b@free.fr>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"bridge@lists.linux-foundation.org"
<bridge@lists.linux-foundation.org>,
"nikolay@nvidia.com" <nikolay@nvidia.com>,
"roopa@nvidia.com" <roopa@nvidia.com>
Subject: Re: [Bridge] [bridge]: STP: no port in blocking state despite a loop when in a network namespace
Date: Wed, 2 Aug 2023 03:45:40 +0000 [thread overview]
Message-ID: <0acf2133dc8f47d3ac40e718ab014b59@boeing.com> (raw)
In-Reply-To: <b1b77fe134e64bfc85394050bd40dff6@boeing.com>
Forwarding related issue:
https://lore.kernel.org/netdev/20230711174934.3871fb61@kernel.org/T/#m4d53064313393cdee86f12ef9313523aa734d681
next prev parent reply other threads:[~2023-08-02 3:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 3:40 [Bridge] [bridge]: STP: no port in blocking state despite a loop when in a network namespace Hasenbosch, Samuel J
2023-08-02 3:45 ` Hasenbosch, Samuel J [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-31 9:17 SPYFF
2021-06-14 16:42 Adel Belhouane
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=0acf2133dc8f47d3ac40e718ab014b59@boeing.com \
--to=samuel.j.hasenbosch@boeing.com \
--cc=bridge@lists.linux-foundation.org \
--cc=bugs.a.b@free.fr \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=roopa@nvidia.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 read-only IMAP folder(s) and NNTP newsgroup(s).