[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190212.095030.1445077555795164973.davem@davemloft.net>
Date: Tue, 12 Feb 2019 09:50:30 -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, devel@...verdev.osuosl.org,
bridge@...ts.linux-foundation.org, jiri@...lanox.com,
andrew@...n.ch, vivien.didelot@...il.com
Subject: Re: [PATCH net-next 0/3] Remove getting
SWITCHDEV_ATTR_ID_PORT_BRIDGE_FLAGS
From: Florian Fainelli <f.fainelli@...il.com>
Date: Mon, 11 Feb 2019 13:17:46 -0800
> AFAICT there is no code that attempts to get the value of the attribute
> SWITCHDEV_ATTR_ID_PORT_BRIDGE_FLAGS while it is used with
> switchdev_port_attr_set().
>
> This is effectively no doing anything and it can slow down future work
> that tries to make modifications in these areas so remove that.
Series applied.
> David, there should be no dependency with previous patch series, but
> again, feedback from Ido and Jiri would be welcome in case this was
> added for a reason.
Ok, is there going to be another respin of that switchdev_ops removal
series?
Powered by blists - more mailing lists