summaryrefslogtreecommitdiffstats
path: root/include/net
diff options
context:
space:
mode:
authorInaky Perez-Gonzalez <inaky@linux.intel.com>2009-09-17 02:53:57 +0200
committerInaky Perez-Gonzalez <inaky@linux.intel.com>2009-10-19 08:56:06 +0200
commit8f90f3ee83dc54e182d6a7548727cbae4b523e6e (patch)
tree8a81fd0076562a5c6e30a652c63fa25343783dc6 /include/net
parentwimax/i2400m: on device stop, clean up pending wake & TX work (diff)
downloadlinux-8f90f3ee83dc54e182d6a7548727cbae4b523e6e.tar.xz
linux-8f90f3ee83dc54e182d6a7548727cbae4b523e6e.zip
wimax/i2400m: cleanup initialization/destruction flow
Currently the i2400m driver was starting in a weird way: registering a network device, setting the device up and then registering a WiMAX device. This is an historic artifact, and was causing issues, a some early reports the device sends were getting lost by issue of the wimax_dev not being registered. Fix said situation by doing the wimax device registration in i2400m_setup() after network device registration and before starting thed device. As well, removed spurious setting of the state to UNINITIALIZED; i2400m.dev_start() does that already. Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com>
Diffstat (limited to 'include/net')
0 files changed, 0 insertions, 0 deletions