From: Andrew Lunn <andrew@lunn.ch>
To: Oleksij Rempel <o.rempel@pengutronix.de>, '@lunn.ch
Cc: Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@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 v2 3/6] net: dsa: qca: ar9331: add forwarding database support'
Date: Fri, 2 Jul 2021 17:14:34 +0200 [thread overview]
Message-ID: <YN8tWtqfRRO7kAlb@lunn.ch> (raw)
In-Reply-To: <20210702101751.13168-4-o.rempel@pengutronix.de>
On Fri, Jul 02, 2021 at 12:17:48PM +0200, Oleksij Rempel wrote:
> This switch provides simple address resolution table, without VLAN or
> multicast specific information.
> With this patch we are able now to read, modify unicast and mulicast
mul_t_icast.
> addresses.
> +static int ar9331_sw_port_fdb_dump(struct dsa_switch *ds, int port,
> + dsa_fdb_dump_cb_t *cb, void *data)
> +{
> + struct ar9331_sw_priv *priv = (struct ar9331_sw_priv *)ds->priv;
> + int cnt = AR9331_SW_NUM_ARL_RECORDS;
> + struct ar9331_sw_fdb _fdb = { 0 };
Why use _fdb? There does not appear to be an fdb?
> +static int ar9331_sw_port_fdb_rmw(struct ar9331_sw_priv *priv,
> + const unsigned char *mac,
> + u8 port_mask_set,
> + u8 port_mask_clr)
> +{
> + struct regmap *regmap = priv->regmap;
> + u32 f0, f1, f2 = 0;
> + u8 port_mask, port_mask_new, status, func;
> + int ret;
Reverse Christmas tree.
> +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);
> +
> + dev_info(priv->dev, "%s(%pM, %x)\n", __func__, mac, port);
dev_dbg()?
Andrew
next prev parent reply other threads:[~2021-07-02 15:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 10:17 [PATCH net-next v2 0/6] ar9331: mainline some parts of switch functionality Oleksij Rempel
2021-07-02 10:17 ` [PATCH net-next v2 1/6] net: dsa: qca: ar9331: reorder MDIO write sequence Oleksij Rempel
2021-07-02 10:17 ` [PATCH net-next v2 2/6] net: dsa: qca: ar9331: make proper initial port defaults Oleksij Rempel
2021-07-02 15:06 ` Andrew Lunn
2021-07-02 10:17 ` [PATCH net-next v2 3/6] net: dsa: qca: ar9331: add forwarding database support Oleksij Rempel
2021-07-02 15:14 ` Andrew Lunn [this message]
2021-07-03 8:56 ` [PATCH net-next v2 3/6] net: dsa: qca: ar9331: add forwarding database support' Oleksij Rempel
2021-07-03 14:33 ` Andrew Lunn
2021-07-02 10:17 ` [PATCH net-next v2 4/6] net: dsa: qca: ar9331: add ageing time support Oleksij Rempel
2021-07-02 10:17 ` [PATCH net-next v2 5/6] net: dsa: qca: ar9331: add bridge support Oleksij Rempel
2021-07-02 10:17 ` [PATCH net-next v2 6/6] net: dsa: qca: ar9331: add vlan support Oleksij Rempel
2021-07-02 20:38 ` [PATCH net-next v2 0/6] ar9331: mainline some parts of switch functionality David Miller
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=YN8tWtqfRRO7kAlb@lunn.ch \
--to=andrew@lunn.ch \
--cc='@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.