Searched hist:f6837ba8c98afcf28ec25f6863a8597274aeefd6 (Results 1 – 6 of 6) sorted by relevance
/linux/net/mac80211/ |
H A D | driver-ops.h | diff f6837ba8c98afcf28ec25f6863a8597274aeefd6 Wed Apr 30 14:19:04 CEST 2014 Johannes Berg <johannes.berg@intel.com> mac80211: handle failed restart/resume better
When the driver fails during HW restart or resume, the whole stack goes into a very confused state with interfaces being up while the hardware is down etc.
Address this by shutting down everything; we'll run into a lot of warnings in the process but that's better than having the whole stack get messed up.
Reviewed-by: Arik Nemtsov <arik@wizery.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
H A D | scan.c | diff f6837ba8c98afcf28ec25f6863a8597274aeefd6 Wed Apr 30 14:19:04 CEST 2014 Johannes Berg <johannes.berg@intel.com> mac80211: handle failed restart/resume better
When the driver fails during HW restart or resume, the whole stack goes into a very confused state with interfaces being up while the hardware is down etc.
Address this by shutting down everything; we'll run into a lot of warnings in the process but that's better than having the whole stack get messed up.
Reviewed-by: Arik Nemtsov <arik@wizery.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
H A D | util.c | diff f6837ba8c98afcf28ec25f6863a8597274aeefd6 Wed Apr 30 14:19:04 CEST 2014 Johannes Berg <johannes.berg@intel.com> mac80211: handle failed restart/resume better
When the driver fails during HW restart or resume, the whole stack goes into a very confused state with interfaces being up while the hardware is down etc.
Address this by shutting down everything; we'll run into a lot of warnings in the process but that's better than having the whole stack get messed up.
Reviewed-by: Arik Nemtsov <arik@wizery.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
H A D | ieee80211_i.h | diff f6837ba8c98afcf28ec25f6863a8597274aeefd6 Wed Apr 30 14:19:04 CEST 2014 Johannes Berg <johannes.berg@intel.com> mac80211: handle failed restart/resume better
When the driver fails during HW restart or resume, the whole stack goes into a very confused state with interfaces being up while the hardware is down etc.
Address this by shutting down everything; we'll run into a lot of warnings in the process but that's better than having the whole stack get messed up.
Reviewed-by: Arik Nemtsov <arik@wizery.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
/linux/net/wireless/ |
H A D | core.c | diff f6837ba8c98afcf28ec25f6863a8597274aeefd6 Wed Apr 30 14:19:04 CEST 2014 Johannes Berg <johannes.berg@intel.com> mac80211: handle failed restart/resume better
When the driver fails during HW restart or resume, the whole stack goes into a very confused state with interfaces being up while the hardware is down etc.
Address this by shutting down everything; we'll run into a lot of warnings in the process but that's better than having the whole stack get messed up.
Reviewed-by: Arik Nemtsov <arik@wizery.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
/linux/include/net/ |
H A D | cfg80211.h | diff f6837ba8c98afcf28ec25f6863a8597274aeefd6 Wed Apr 30 14:19:04 CEST 2014 Johannes Berg <johannes.berg@intel.com> mac80211: handle failed restart/resume better
When the driver fails during HW restart or resume, the whole stack goes into a very confused state with interfaces being up while the hardware is down etc.
Address this by shutting down everything; we'll run into a lot of warnings in the process but that's better than having the whole stack get messed up.
Reviewed-by: Arik Nemtsov <arik@wizery.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|