[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <877enrzp42.fsf@weeman.i-did-not-set--mail-host-address--so-tickle-me>
Date: Fri, 25 May 2018 12:17:33 -0400
From: Vivien Didelot <vivien.didelot@...oirfairelinux.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, f.fainelli@...il.com,
nikolay@...ulusnetworks.com
Subject: Re: [PATCH net-next 6/7] net: bridge: Notify about bridge VLANs
Hi Petr,
Petr Machata <petrm@...lanox.com> writes:
> 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>
> + } else {
> + err = br_switchdev_port_obj_add(dev, v->vid, flags);
> + if (err && err != -EOPNOTSUPP)
> + goto out;
> }
Except that br_switchdev_port_obj_add taking vid and flags arguments
seems confusing to me, the change looks good:
Reviewed-by: Vivien Didelot <vivien.didelot@...oirfairelinux.com>
Thanks,
Vivien
Powered by blists - more mailing lists