[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YDb56X8EzlobB/2n@lunn.ch>
Date: Thu, 25 Feb 2021 02:14:17 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Vladimir Oltean <olteanv@...il.com>
Cc: netdev@...r.kernel.org, Florian Fainelli <f.fainelli@...il.com>,
Vivien Didelot <vivien.didelot@...il.com>,
Jiri Pirko <jiri@...nulli.us>,
Ido Schimmel <idosch@...sch.org>,
DENG Qingfang <dqfext@...il.com>,
Tobias Waldekranz <tobias@...dekranz.com>,
George McCollister <george.mccollister@...il.com>,
Horatiu Vultur <horatiu.vultur@...rochip.com>,
Kurt Kanzenbach <kurt@...utronix.de>
Subject: Re: [RFC PATCH net-next 06/12] Documentation: networking: dsa:
document the port_bridge_flags method
> + the bridge port flags for the CPU port. The assumption is that address
> + learning should be statically enabled (if supported by the hardware) on the
> + CPU port, and flooding towards the CPU port should also be enabled, in lack
> + of an explicit address filtering mechanism in the DSA core.
Hi Vladimir
"in lack of" is a bit odd wording. Maybe "due to a lack of"
Reviewed-by: Andrew Lunn <andrew@...n.ch>
Andrew
Powered by blists - more mailing lists