From: Vladimir Oltean <olteanv@gmail.com>
To: "A. Sverdlin" <alexander.sverdlin@siemens.com>
Cc: netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
linux-kernel@vger.kernel.org,
Egil Hjelmeland <privat@egil-hjelmeland.no>
Subject: Re: [PATCH] net: dsa: lan9303: allow vid != 0 in port_fdb_{add|del} methods
Date: Wed, 31 May 2023 18:16:20 +0300 [thread overview]
Message-ID: <20230531151620.rqdaf2dlp5jsn6mk@skbuf> (raw)
In-Reply-To: <20230531143826.477267-1-alexander.sverdlin@siemens.com>
On Wed, May 31, 2023 at 04:38:26PM +0200, A. Sverdlin wrote:
> From: Alexander Sverdlin <alexander.sverdlin@siemens.com>
>
> LAN9303 doesn't associate FDB (ALR) entries with VLANs, it has just one
> global Address Logic Resolution table [1].
>
> Ignore VID in port_fdb_{add|del} methods, go on with the global table. This
> is the same semantics as hellcreek or RZ/N1 implement.
>
> Visible symptoms:
> LAN9303_MDIO 5b050000.ethernet-1:00: port 2 failed to delete 00:xx:xx:xx:xx:cf vid 1 from fdb: -2
> LAN9303_MDIO 5b050000.ethernet-1:00: port 2 failed to add 00:xx:xx:xx:xx:cf vid 1 to fdb: -95
>
> [1] https://ww1.microchip.com/downloads/en/DeviceDoc/00002308A.pdf
>
> Fixes: 0620427ea0d6 ("net: dsa: lan9303: Add fdb/mdb manipulation")
> Signed-off-by: Alexander Sverdlin <alexander.sverdlin@siemens.com>
> ---
Thanks for taking a look. Although it would probably be safer to add:
Fixes: 2fd186501b1c ("net: dsa: be louder when a non-legacy FDB operation fails")
since I'm not sure it has a reason to be backported beyond that. Anyway:
Reviewed-by: Vladimir Oltean <olteanv@gmail.com>
Yuck.
next prev parent reply other threads:[~2023-05-31 15:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 14:38 [PATCH] net: dsa: lan9303: allow vid != 0 in port_fdb_{add|del} methods A. Sverdlin
2023-05-31 15:16 ` Vladimir Oltean [this message]
2023-05-31 15:20 ` Sverdlin, Alexander
2023-05-31 15:35 ` Vladimir Oltean
2023-06-01 4:41 ` Jakub Kicinski
2023-06-01 8:32 ` Vladimir Oltean
2023-06-02 4:50 ` patchwork-bot+netdevbpf
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=20230531151620.rqdaf2dlp5jsn6mk@skbuf \
--to=olteanv@gmail.com \
--cc=alexander.sverdlin@siemens.com \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=privat@egil-hjelmeland.no \
/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