[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAOiHx=nZvCGf9f5_07pUS+nS3FOrn9e2-eoyAkOw_oTHO7Aujw@mail.gmail.com>
Date: Wed, 26 Nov 2025 10:07:50 +0100
From: Jonas Gorski <jonas.gorski@...il.com>
To: Vladimir Oltean <olteanv@...il.com>
Cc: Florian Fainelli <florian.fainelli@...adcom.com>, Andrew Lunn <andrew@...n.ch>,
"David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Álvaro Fernández Rojas <noltari@...il.com>,
Florian Fainelli <f.fainelli@...il.com>, netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 4/7] net: dsa: b53: fix CPU port unicast ARL
entries for BCM5325/65
On Tue, Nov 25, 2025 at 9:42 PM Vladimir Oltean <olteanv@...il.com> wrote:
>
> On Tue, Nov 25, 2025 at 08:51:47AM +0100, Jonas Gorski wrote:
> > On BCM5325 and BCM5365, unicast ARL entries use 8 as the value for the
> > CPU port, so we need to translate it to/from 5 as used for the CPU port
> > at most other places.
> > + ent->port = (mac_vid >> ARLTBL_DATA_PORT_ID_S_25) &
> > + ARLTBL_DATA_PORT_ID_MASK_25;
> > + if (!is_multicast_ether_addr(ent->mac) && ent->port == B53_CPU_PORT)
> > + ent->port = B53_CPU_PORT_25;
>
> Why not use is_unicast_ether_addr() to have a more clear correlation
> between the commit message and the code?
There is a very simple explanation for that: I didn't know it existed.
Will change it for v2.
Thanks for the review,
Jonas
Powered by blists - more mailing lists