From: Vladimir Oltean <olteanv@gmail.com> To: Oleksij Rempel <o.rempel@pengutronix.de> Cc: Andrew Lunn <andrew@lunn.ch>, Vivien Didelot <vivien.didelot@gmail.com>, Florian Fainelli <f.fainelli@gmail.com>, "David S. Miller" <davem@davemloft.net>, Jakub Kicinski <kuba@kernel.org>, Russell King <linux@armlinux.org.uk>, Pengutronix Kernel Team <kernel@pengutronix.de>, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org Subject: Re: [PATCH net-next v3 3/6] net: dsa: qca: ar9331: add forwarding database support Date: Mon, 2 Aug 2021 18:37:23 +0300 [thread overview] Message-ID: <20210802153723.vp4phpinclsuhlzz@skbuf> (raw) In-Reply-To: <20210802131037.32326-4-o.rempel@pengutronix.de> On Mon, Aug 02, 2021 at 03:10:34PM +0200, Oleksij Rempel wrote: > +static int ar9331_sw_port_fdb_add(struct dsa_switch *ds, int port, > + const unsigned char *mac, u16 vid) > +{ > + struct ar9331_sw_priv *priv = (struct ar9331_sw_priv *)ds->priv; > + u16 port_mask = BIT(port); > + > + if (vid) > + return -EINVAL; When did you test this patch last time on net-next? Asking because when a port joins a VLAN-aware bridge, it will replay the FDB entries towards the bridge, which include a VLAN-unaware FDB entry with VID 0, and a VLAN-aware one with the bridge's default_pvid. If you return -EINVAL, that br_fdb_replay call will fail and you will fail to join the bridge. > + > + return ar9331_sw_port_fdb_rmw(priv, mac, port_mask, 0); > +} > + > +static int ar9331_sw_port_fdb_del(struct dsa_switch *ds, int port, > + const unsigned char *mac, u16 vid) > +{ > + struct ar9331_sw_priv *priv = (struct ar9331_sw_priv *)ds->priv; > + u16 port_mask = BIT(port); > + > + if (vid) > + return -EINVAL; > + > + return ar9331_sw_port_fdb_rmw(priv, mac, 0, port_mask); > +}
next prev parent reply other threads:[~2021-08-02 15:37 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-02 13:10 [PATCH net-next v3 0/6] ar9331: mainline some parts of switch functionality Oleksij Rempel 2021-08-02 13:10 ` [PATCH net-next v3 1/6] net: dsa: qca: ar9331: reorder MDIO write sequence Oleksij Rempel 2021-08-02 14:00 ` Vladimir Oltean 2021-08-02 13:10 ` [PATCH net-next v3 2/6] net: dsa: qca: ar9331: make proper initial port defaults Oleksij Rempel 2021-08-02 14:03 ` Vladimir Oltean 2021-08-02 19:45 ` Andrew Lunn 2021-08-03 6:36 ` Oleksij Rempel 2021-08-02 19:42 ` Andrew Lunn 2021-08-02 13:10 ` [PATCH net-next v3 3/6] net: dsa: qca: ar9331: add forwarding database support Oleksij Rempel 2021-08-02 15:37 ` Vladimir Oltean [this message] 2021-08-02 13:10 ` [PATCH net-next v3 4/6] net: dsa: qca: ar9331: add ageing time support Oleksij Rempel 2021-08-02 13:10 ` [PATCH net-next v3 5/6] net: dsa: qca: ar9331: add bridge support Oleksij Rempel 2021-08-02 14:55 ` Vladimir Oltean 2021-08-07 23:08 ` Vladimir Oltean 2021-08-09 5:04 ` Oleksij Rempel 2021-08-02 13:10 ` [PATCH net-next v3 6/6] net: dsa: qca: ar9331: add vlan support Oleksij Rempel 2021-08-02 14:50 ` Vladimir Oltean
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=20210802153723.vp4phpinclsuhlzz@skbuf \ --to=olteanv@gmail.com \ --cc=andrew@lunn.ch \ --cc=davem@davemloft.net \ --cc=f.fainelli@gmail.com \ --cc=kernel@pengutronix.de \ --cc=kuba@kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mips@vger.kernel.org \ --cc=linux@armlinux.org.uk \ --cc=netdev@vger.kernel.org \ --cc=o.rempel@pengutronix.de \ --cc=vivien.didelot@gmail.com \ --subject='Re: [PATCH net-next v3 3/6] net: dsa: qca: ar9331: add forwarding database support' \ /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
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).