From: Florian Fainelli <f.fainelli@gmail.com>
To: netdev@vger.kernel.org
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
linux-kernel@vger.kernel.org (open list),
Matthew Hagan <mnhagan88@gmail.com>
Subject: [PATCH net-next 0/2] net: dsa: b53: Remove unconditional CPU VLAN tagging
Date: Mon, 7 Jun 2021 15:08:41 -0700 [thread overview]
Message-ID: <20210607220843.3799414-1-f.fainelli@gmail.com> (raw)
This patch series removes the unconditional egress tagging of VLANs
added to a b53 switch's CPU port. This had led to adding the
untag_bridge_pvid attribute in the DSA framework and is causing problems
with stacking of switches such as the configuration being used by
Matthew.
Since we use Broadcom tags for all of the supported switches nowadays
the original situation that led to doing this unconditional egress
tagging is no longer warranted.
Florian Fainelli (2):
net: dsa: b53: Do not force tagging on CPU port VLANs
net: dsa: Remove bridge PVID untagging
drivers/net/dsa/b53/b53_common.c | 5 ++-
include/net/dsa.h | 8 -----
net/dsa/dsa.c | 9 -----
net/dsa/dsa_priv.h | 59 --------------------------------
4 files changed, 2 insertions(+), 79 deletions(-)
--
2.25.1
next reply other threads:[~2021-06-07 22:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 22:08 Florian Fainelli [this message]
2021-06-07 22:08 ` [PATCH net-next 1/2] net: dsa: b53: Do not force tagging on CPU port VLANs Florian Fainelli
2021-06-07 22:22 ` Vladimir Oltean
2021-06-07 22:31 ` Florian Fainelli
2021-06-07 22:36 ` Florian Fainelli
2021-06-07 22:08 ` [PATCH net-next 2/2] net: dsa: Remove bridge PVID untagging Florian Fainelli
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=20210607220843.3799414-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mnhagan88@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=vivien.didelot@gmail.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