From: "Hasenbosch, Samuel J" <Samuel.J.Hasenbosch@boeing.com>
To: "stephen@networkplumber.org" <stephen@networkplumber.org>
Cc: "andrew@lunn.ch" <andrew@lunn.ch>,
"hcoin@quietfountain.com" <hcoin@quietfountain.com>,
"kuniyu@amazon.com" <kuniyu@amazon.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: RE: Re: llc needs namespace awareness asap, was Re: Patch fixing STP if bridge in non-default namespace.
Date: Wed, 2 Aug 2023 03:45:10 +0000 [thread overview]
Message-ID: <60bf35338d424beca3d9ba60deb1839c@boeing.com> (raw)
In-Reply-To: <35b7a25672c1405383960557ea4d6131@boeing.com>
Forwarding related issue:
https://lore.kernel.org/netdev/cf3001de-4ee2-45f2-83d3-3c878b85d628@free.fr/
next parent reply other threads:[~2023-08-02 3:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <35b7a25672c1405383960557ea4d6131@boeing.com>
2023-08-02 3:45 ` Hasenbosch, Samuel J [this message]
2023-08-02 3:50 ` llc needs namespace awareness asap, was Re: Patch fixing STP if bridge in non-default namespace Kuniyuki Iwashima
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=60bf35338d424beca3d9ba60deb1839c@boeing.com \
--to=samuel.j.hasenbosch@boeing.com \
--cc=andrew@lunn.ch \
--cc=hcoin@quietfountain.com \
--cc=kuniyu@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/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).