[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e87b67e1-fdaf-a748-d424-578a599b5441@cumulusnetworks.com>
Date: Wed, 30 May 2018 18:58:13 +0300
From: Nikolay Aleksandrov <nikolay@...ulusnetworks.com>
To: Petr Machata <petrm@...lanox.com>, netdev@...r.kernel.org,
devel@...verdev.osuosl.org, bridge@...ts.linux-foundation.org
Cc: jiri@...lanox.com, idosch@...lanox.com, davem@...emloft.net,
razvan.stefanescu@....com, gregkh@...uxfoundation.org,
stephen@...workplumber.org, andrew@...n.ch,
vivien.didelot@...oirfairelinux.com, f.fainelli@...il.com,
dan.carpenter@...cle.com
Subject: Re: [PATCH net-next v4 7/8] net: bridge: Notify about bridge VLANs
On 30/05/18 04:00, Petr Machata wrote:
> A driver might need to react to changes in settings of brentry VLANs.
> Therefore send switchdev port notifications for these as well. Reuse
> SWITCHDEV_OBJ_ID_PORT_VLAN for this purpose. Listeners should use
> netif_is_bridge_master() on orig_dev to determine whether the
> notification is about a bridge port or a bridge.
>
> Signed-off-by: Petr Machata <petrm@...lanox.com>
> ---
> net/bridge/br_vlan.c | 28 +++++++++++++++++++++++++---
> 1 file changed, 25 insertions(+), 3 deletions(-)
>
LGTM,
Reviewed-by: Nikolay Aleksandrov <nikolay@...ulusnetworks.com>
Powered by blists - more mailing lists