libertas: fix misuse of netdev_priv() and dev->ml_priv
The mesh and radiotap interfaces need to use the same private data as the main wifi interface. If the main wifi interface uses netdev_priv(), but the other interfaces ->ml_priv, there's no way to figure out where the private data actually is in the WEXT handlers and netdevice callbacks. So make everything use ->ml_priv. Fixes botched netdev_priv() conversion introduced by "netdevice libertas: Fix directly reference of netdev->priv", though admittedly libertas' use of ->priv was somewhat "special". Signed-off-by:Kiran Divekar <dkiran@marvell.com> Acked-by:
Dan Williams <dcbw@redhat.com> Tested-by:
Chris Ball <cjb@laptop.org> Signed-off-by:
John W. Linville <linville@tuxdriver.com>
Showing
- drivers/net/wireless/libertas/ethtool.c 6 additions, 6 deletionsdrivers/net/wireless/libertas/ethtool.c
- drivers/net/wireless/libertas/if_usb.c 2 additions, 2 deletionsdrivers/net/wireless/libertas/if_usb.c
- drivers/net/wireless/libertas/main.c 16 additions, 15 deletionsdrivers/net/wireless/libertas/main.c
- drivers/net/wireless/libertas/persistcfg.c 8 additions, 8 deletionsdrivers/net/wireless/libertas/persistcfg.c
- drivers/net/wireless/libertas/scan.c 2 additions, 2 deletionsdrivers/net/wireless/libertas/scan.c
- drivers/net/wireless/libertas/tx.c 1 addition, 1 deletiondrivers/net/wireless/libertas/tx.c
- drivers/net/wireless/libertas/wext.c 36 additions, 36 deletionsdrivers/net/wireless/libertas/wext.c
Loading
Please register or sign in to comment