From: Florian Fainelli <f.fainelli@gmail.com>
To: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Cc: Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
open list <linux-kernel@vger.kernel.org>,
vladimir.oltean@nxp.com, olteanv@gmail.com, nikolay@nvidia.com
Subject: Re: [PATCH net-next v2 0/2] net: dsa: b53: Configure VLANs while not filtering
Date: Wed, 23 Sep 2020 13:49:54 -0700 [thread overview]
Message-ID: <bfccb4fd-0768-79e8-0085-df63ecc0d376@gmail.com> (raw)
In-Reply-To: <20200923204514.3663635-1-f.fainelli@gmail.com>
On 9/23/20 1:45 PM, Florian Fainelli wrote:
> Hi David, Jakub,
>
> These two patches allow the b53 driver which always configures its CPU
> port as egress tagged to behave correctly with VLANs being always
> configured whenever a port is added to a bridge.
>
> Vladimir provides a patch that aligns the bridge with vlan_filtering=0
> receive path to behave the same as vlan_filtering=1. Per discussion with
> Nikolay, this behavior is deemed to be too DSA specific to be done in
> the bridge proper.
>
> This is a preliminary series for Vladimir to make
> configure_vlan_while_filtering the default behavior for all DSA drivers
> in the future.
David, Jakub, there is an unnecessary header inclusion in
net/dsa/tag_brcm.c in the second patch and the description at the end of
the commit was not updated, let me send a v3 right away.
--
Florian
next prev parent reply other threads:[~2020-09-23 20:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 20:45 [PATCH net-next v2 0/2] net: dsa: b53: Configure VLANs while not filtering Florian Fainelli
2020-09-23 20:45 ` [PATCH net-next v2 1/2] net: dsa: untag the bridge pvid from rx skbs Florian Fainelli
2020-09-23 20:45 ` [PATCH net-next v2 2/2] net: dsa: b53: Configure VLANs while not filtering Florian Fainelli
2020-09-23 21:23 ` Vladimir Oltean
2020-09-23 20:49 ` Florian Fainelli [this message]
2020-09-23 20:51 ` [PATCH net-next v2 0/2] " Vladimir Oltean
2020-09-23 21:30 ` Vladimir Oltean
2020-09-23 21:39 ` 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=bfccb4fd-0768-79e8-0085-df63ecc0d376@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=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=olteanv@gmail.com \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@nxp.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