[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <af122e70-d073-cd83-541c-b3a0125c7cfb@nvidia.com>
Date: Mon, 7 Feb 2022 12:51:05 +0200
From: Nikolay Aleksandrov <nikolay@...dia.com>
To: Hans Schultz <schultz.hans@...il.com>, <davem@...emloft.net>,
<kuba@...nel.org>
CC: <netdev@...r.kernel.org>,
Hans Schultz <schultz.hans+netdev@...il.com>,
Roopa Prabhu <roopa@...dia.com>, Andrew Lunn <andrew@...n.ch>,
Vivien Didelot <vivien.didelot@...il.com>,
Florian Fainelli <f.fainelli@...il.com>,
"Vladimir Oltean" <olteanv@...il.com>,
<bridge@...ts.linux-foundation.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH net-next 2/4] net: bridge: dsa: Add support for offloading
of locked port flag
On 07/02/2022 12:07, Hans Schultz wrote:
> Various switchcores support setting ports in locked mode, so that
> clients behind locked ports cannot send traffic through the port
> unless a fdb entry is added with the clients MAC address.
>
> Among the switchcores that support this feature is the Marvell
> mv88e6xxx family.
>
> Signed-off-by: Hans Schultz <schultz.hans+netdev@...il.com>
> ---
> net/bridge/br_switchdev.c | 2 +-
> net/dsa/port.c | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
Hi,
For some reason I still haven't received patch 01 which adds this new flag,
so I'll comment on this patch first.
These should be 2 separate patches, there is no bridge: dsa:.
Please break them into a bridge: and dsa: parts that add the flag, it also
makes it easier for people who have to backport patches and fixes later.
In addition please mention in the commit message why the flag is
added there, i.e. in order to allow to be offloaded.
Thanks,
Nik
Powered by blists - more mailing lists