Re: [Bridge] [RFC net-next 0/3] net: bridge: Allow CPU port configuration

On 11/23/2016 05:48 AM, Ido Schimmel wrote: > Hi Florian, > > On Tue, Nov 22, 2016 at 09:56:30AM -0800, Florian Fainelli wrote: >> On 11/22/2016 09:41 AM, Ido Schimmel wrote: >>> Hi Florian, >>> >>> On Mon, Nov 21, 2016 at 11:09:22AM -0800, Florian Fainelli wrote: Hi all, This

Re: [Bridge] [RFC net-next 0/3] net: bridge: Allow CPU port configuration

Hi Florian, On Tue, Nov 22, 2016 at 09:56:30AM -0800, Florian Fainelli wrote: > On 11/22/2016 09:41 AM, Ido Schimmel wrote: > > Hi Florian, > > > > On Mon, Nov 21, 2016 at 11:09:22AM -0800, Florian Fainelli wrote: > >> Hi all, > >> > >> This patch series allows using the bridge master interface

Re: [Bridge] [RFC net-next 0/3] net: bridge: Allow CPU port configuration

Hi Florian, On Mon, Nov 21, 2016 at 11:09:22AM -0800, Florian Fainelli wrote: > Hi all, > > This patch series allows using the bridge master interface to configure > an Ethernet switch port's CPU/management port with different VLAN attributes > than > those of the bridge downstream

Re: [Bridge] [RFC net-next 0/3] net: bridge: Allow CPU port configuration

On 11/22/2016 02:08 PM, Jiri Pirko wrote: > Tue, Nov 22, 2016 at 06:48:29PM CET, and...@lunn.ch wrote: >> Hi Ido >> >>> First of all, I want to be sure that when we say "CPU port", we're >>> talking about the same thing. In mlxsw, the CPU port is a pipe between >>> the device and the host, through

Re: [Bridge] [RFC net-next 0/3] net: bridge: Allow CPU port configuration

On 11/22/2016 09:41 AM, Ido Schimmel wrote: > Hi Florian, > > On Mon, Nov 21, 2016 at 11:09:22AM -0800, Florian Fainelli wrote: >> Hi all, >> >> This patch series allows using the bridge master interface to configure >> an Ethernet switch port's CPU/management port with different VLAN attributes

Re: [Bridge] [RFC net-next 0/3] net: bridge: Allow CPU port configuration

Hi Florian, Florian Fainelli writes: > This patch series allows using the bridge master interface to configure > an Ethernet switch port's CPU/management port with different VLAN attributes > than > those of the bridge downstream ports/members. > > Jiri, Ido, Andrew,