linux-stable/drivers/staging/wlan-ng
Emil Goode 01f8a27e3c staging: wlan-ng: Fix problem with wrong arguments
The function pointer scan in struct cfg80211_ops is not
supposed to be assigned a function with a struct net_device
pointer as an argument. Instead access the net_device struct
in the following way:

struct net_device *dev = request->wdev->netdev;

sparse gives these warnings:

drivers/staging/wlan-ng/cfg80211.c:726:17: warning:
        incorrect type in initializer (incompatible argument 2
        (different base types))
        expected int ( *scan )( ... )
        got int ( extern [toplevel] *<noident> )( ... )

drivers/staging/wlan-ng/cfg80211.c:726:2: warning:
        initialization from incompatible pointer type [enabled by default]

drivers/staging/wlan-ng/cfg80211.c:726:2: warning:
        (near initialization for ‘prism2_usb_cfg_ops.scan’)
        [enabled by default]

Signed-off-by: Emil Goode <emilgoode@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2012-09-04 12:23:52 -07:00
..
cfg80211.c staging: wlan-ng: Fix problem with wrong arguments 2012-09-04 12:23:52 -07:00
hfa384x.h
hfa384x_usb.c
Kconfig
Makefile
p80211conv.c
p80211conv.h
p80211hdr.h
p80211ioctl.h
p80211meta.h
p80211metadef.h
p80211metastruct.h
p80211mgmt.h
p80211msg.h
p80211netdev.c staging: wlan-ng: p80211netdev.c: fixed checkpatch error 2012-02-24 11:59:57 -08:00
p80211netdev.h
p80211req.c
p80211req.h
p80211types.h
p80211wep.c
prism2fw.c staging: reduce stack usage in prism2fw.c 2012-06-25 10:00:53 -07:00
prism2mgmt.c Staging: wlan-ng: off by one in prism2mgmt_scan_results() 2012-04-18 16:59:03 -07:00
prism2mgmt.h
prism2mib.c
prism2sta.c staging/wlan-ng: use kzalloc rather using kmalloc at create_wlan 2012-07-16 19:21:37 -07:00
prism2usb.c USB: convert drivers/staging/* to use module_usb_driver() 2011-11-18 09:42:11 -08:00
README

TODO:
	- checkpatch.pl cleanups
	- sparse warnings
	- move to use the in-kernel wireless stack

Please send any patches or complaints about this driver to Greg
Kroah-Hartman <greg@kroah.com> and don't bother the upstream wireless
kernel developers about it, they want nothing to do with it.