[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20190206.141810.950568527074058350.davem@davemloft.net>
Date: Wed, 06 Feb 2019 14:18:10 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: f.fainelli@...il.com
Cc: netdev@...r.kernel.org, idosch@...lanox.com,
linux-kernel@...r.kernel.org, linux-rdma@...r.kernel.org,
oss-drivers@...ronome.com, devel@...verdev.osuosl.org,
bridge@...ts.linux-foundation.org
Subject: Re: [PATCH net-next v4 00/12] net: Introduce
ndo_get_port_parent_id()
From: David Miller <davem@...emloft.net>
Date: Wed, 06 Feb 2019 13:50:50 -0800 (PST)
> From: Florian Fainelli <f.fainelli@...il.com>
> Date: Wed, 6 Feb 2019 09:45:34 -0800
>
>> Based on discussion with Ido and feedback from Jakub there are clearly
>> two classes of users that implement SWITCHDEV_ATTR_ID_PORT_PARENT_ID:
>>
>> - PF/VF drivers which typically only implement return the port's parent
>> ID, yet have to implement switchdev_port_attr_get() just for that
>>
>> - Ethernet switch drivers: mlxsw, ocelot, DSA, etc. which implement more
>> attributes which we want to be able to eventually veto in the context
>> of the caller, thus making them candidates for using a blocking notifier
>> chain
>>
>> Changes in v4:
> ..
>
> Series applied, thanks Florian.
>
> I'll push this out to net-next after my build tests complete.
I had to remove the unused variable 'rocker' to kill a warning introduced
by patch #8.
Just FYI...
Powered by blists - more mailing lists