From mboxrd@z Thu Jan 1 00:00:00 1970 From: Florian Fainelli Subject: Re: [PATCH net-next v4 5/8] dsa: port: Ignore bridge VLAN events Date: Tue, 29 May 2018 19:13:20 -0700 Message-ID: <40c2c3fc-c892-69fa-9a9c-1a23d37ce28f@gmail.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: jiri@mellanox.com, idosch@mellanox.com, davem@davemloft.net, razvan.stefanescu@nxp.com, gregkh@linuxfoundation.org, stephen@networkplumber.org, andrew@lunn.ch, vivien.didelot@savoirfairelinux.com, nikolay@cumulusnetworks.com, dan.carpenter@oracle.com To: Petr Machata , netdev@vger.kernel.org, devel@driverdev.osuosl.org, bridge@lists.linux-foundation.org Return-path: Received: from mail-io0-f194.google.com ([209.85.223.194]:43984 "EHLO mail-io0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754845AbeE3CNX (ORCPT ); Tue, 29 May 2018 22:13:23 -0400 Received: by mail-io0-f194.google.com with SMTP id t6-v6so1258318iob.10 for ; Tue, 29 May 2018 19:13:23 -0700 (PDT) In-Reply-To: Content-Language: en-US Sender: netdev-owner@vger.kernel.org List-ID: On 05/29/2018 05:59 PM, Petr Machata wrote: > A follow-up patch enables emitting VLAN notifications for the bridge CPU > port in addition to the existing slave port notifications. These > notifications have orig_dev set to the bridge in question. > > Because there's no specific support for these VLANs, just ignore the > notifications to maintain the current behavior. > > Signed-off-by: Petr Machata > Reviewed-by: Vivien Didelot Reviewed-by: Florian Fainelli -- Florian