summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorInaky Perez-Gonzalez <inaky@linux.intel.com>2009-10-07 22:57:39 +0900
committerInaky Perez-Gonzalez <inaky@linux.intel.com>2009-10-19 15:56:21 +0900
commit0c96859d7a5f0286ed70d3c4e140ac6816a350da (patch)
tree1b1553333c356bd477bc20b9ed95705d8ef3ca89
parent46c501473d0a6fa62435dfd65c6884e1fd63b327 (diff)
downloadlinux-stable-0c96859d7a5f0286ed70d3c4e140ac6816a350da.tar.gz
linux-stable-0c96859d7a5f0286ed70d3c4e140ac6816a350da.tar.bz2
linux-stable-0c96859d7a5f0286ed70d3c4e140ac6816a350da.zip
wimax/i2400m: Let device's status reports change the device state
Currently __i2400m_dev_start was forcing, after uploading firmware and doing a few checks to WIMAX_ST_UNINITIALIZED. This can be overriding state changes that the device might have caused by sending reports; thus it makes more sense to remove it and let the device update the status on its own by sending reports. Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com>
-rw-r--r--drivers/net/wimax/i2400m/driver.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/drivers/net/wimax/i2400m/driver.c b/drivers/net/wimax/i2400m/driver.c
index 42102ebad1ad..cc900b99e60a 100644
--- a/drivers/net/wimax/i2400m/driver.c
+++ b/drivers/net/wimax/i2400m/driver.c
@@ -398,7 +398,6 @@ retry:
result = i2400m_check_mac_addr(i2400m);
if (result < 0)
goto error_check_mac_addr;
- wimax_state_change(wimax_dev, WIMAX_ST_UNINITIALIZED);
result = i2400m_dev_initialize(i2400m);
if (result < 0)
goto error_dev_initialize;