[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <15407e4b247e91fd8326b1013d1a8640@kapio-technology.com>
Date: Tue, 23 Aug 2022 13:41:51 +0200
From: netdev@...io-technology.com
To: Ido Schimmel <idosch@...dia.com>
Cc: Vladimir Oltean <olteanv@...il.com>, davem@...emloft.net,
kuba@...nel.org, netdev@...r.kernel.org,
Andrew Lunn <andrew@...n.ch>,
Vivien Didelot <vivien.didelot@...il.com>,
Florian Fainelli <f.fainelli@...il.com>,
Eric Dumazet <edumazet@...gle.com>,
Paolo Abeni <pabeni@...hat.com>, Jiri Pirko <jiri@...nulli.us>,
Ivan Vecera <ivecera@...hat.com>,
Roopa Prabhu <roopa@...dia.com>,
Nikolay Aleksandrov <razor@...ckwall.org>,
Shuah Khan <shuah@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
linux-kernel@...r.kernel.org, bridge@...ts.linux-foundation.org,
linux-kselftest@...r.kernel.org
Subject: Re: [PATCH v4 net-next 3/6] drivers: net: dsa: add locked fdb entry
flag to drivers
On 2022-08-23 08:48, Ido Schimmel wrote:
>
> I'm not good at naming, but "blackhole" is at least consistent with
> what
> we already have for routes and nexthop objects.
>
I have changed it the name "masked", as that is also the term used in
the documentation for the zero-DPV entries, and I think that it will
generally be a more accepted term.
Thus the name of the flag is now "BR_FDB_ENTRY_MASKED".
I hope that is fine with you?
Powered by blists - more mailing lists