diff options
author | David S. Miller <davem@davemloft.net> | 2015-04-02 14:05:02 -0400 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2015-04-02 14:05:02 -0400 |
commit | e4a924f5768c55002c02ceba9b9f86824c35f956 (patch) | |
tree | ae8db8c41d5950644db9d4f5e609f228df958e57 /drivers/net/wireless/iwlwifi/dvm/ucode.c | |
parent | 033f46b3c13d4072d8ee6b26dd1e90fdd06895d0 (diff) | |
parent | a45253bf32bf49cdb2807bad212b84f5ab51ac26 (diff) | |
download | op-kernel-dev-e4a924f5768c55002c02ceba9b9f86824c35f956.zip op-kernel-dev-e4a924f5768c55002c02ceba9b9f86824c35f956.tar.gz |
Merge branch 'netdev_iflink_remove'
Nicolas Dichtel says:
====================
Remove iflink field from the net_device structure
The first goal of this series was to advertise the veth peer via the IFLA_LINK
attribute, but iflink was not ready for network namespaces.
The iflink of an interface should be set to its ifindex for a physical interface
and to another value (0 if not relevant) for a virtual interface.
This was not the case for some interfaces, like vxlan, bond, or bridge for
example.
There is also a risk, if the targeted interface moves to another netns, that the
ifindex changes without updating corresponding iflink fields (eg. vlan).
Moving the management of this property into virtual interface drivers allows to
better handle this last case because most of virtual interface drivers have a
pointer to the link netdevice.
Anyway, dev->iflink value was always a copy of some internal data of the virtual
interface driver, thus let's use these internal data directly.
So, this series removes the iflink field and let the drivers manage it.
Only the last patch was present in the v1, but I fully rework it.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/wireless/iwlwifi/dvm/ucode.c')
0 files changed, 0 insertions, 0 deletions