Inaky Perez-Gonzalez 94c7f2d495 wimax: oops: wimax_dev_add() is the only one that can initialize the state ... When a new wimax_dev is created, it's state has to be __WIMAX_ST_NULL until wimax_dev_add() is succesfully called. This allows calls into the stack that happen before said time to be rejected. Until now, the state was being set (by mistake) to UNINITIALIZED, which was allowing calls such as wimax_report_rfkill_hw() to go through even when a call to wimax_dev_add() had failed; that was causing an oops when touching uninitialized data. This situation is normal when the device starts reporting state before the whole initialization has been completed. It just has to be dealt with. Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com>		2009-05-06 13:48:37 -07:00
..
debug-levels.h
debugfs.c	wimax: fix build issue when debugfs is disabled	2009-01-29 17:18:31 -08:00
id-table.c	wimax: fix oops in wimax_dev_get_by_genl_info() when looking up non-wimax iface	2009-02-12 17:00:20 -08:00
Kconfig	trivial: fix typos/grammar errors in Kconfig texts	2009-03-30 15:22:01 +02:00
Makefile	wimax: Makefile, Kconfig and docbook linkage for the stack	2009-01-07 10:00:17 -08:00
op-msg.c	wimax: fix oops if netlink fails to add attribute	2009-05-06 13:48:36 -07:00
op-reset.c	wimax: basic API: kernel/user messaging, rfkill and reset	2009-01-07 10:00:17 -08:00
op-rfkill.c	wimax: testing for rfkill support should also test for CONFIG_RFKILL_MODULE	2009-01-08 11:08:01 -08:00
stack.c	wimax: oops: wimax_dev_add() is the only one that can initialize the state	2009-05-06 13:48:37 -07:00
wimax-internal.h