diff options
| author | David Kilroy <kilroyd@googlemail.com> | 2010-12-05 15:45:58 +0000 |
|---|---|---|
| committer | AK <andi@firstfloor.org> | 2011-02-06 11:03:42 -0800 |
| commit | 6660a58806566b5b452b8b6458be90526fbec054 (patch) | |
| tree | 4e969eb4381ba8ae4ae2d0744ab147613abe2571 /arch/x86 | |
| parent | c0be80088ed2d65565fa02732030a7bfc9a7a0c6 (diff) | |
orinoco: clear countermeasure setting on commit
commit ba34fcee476d11e7c9df95932787a22a96ff6e68 upstream.
... and interface up.
In these situations, you are usually trying to connect to a new AP, so
keeping TKIP countermeasures active is confusing. This is already how
the driver behaves (inadvertently). However, querying SIOCGIWAUTH may
tell userspace that countermeasures are active when they aren't.
Clear the setting so that the reporting matches what the driver has
done..
Signed-off by: David Kilroy <kilroyd@googlemail.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Andi Kleen <ak@linux.intel.com>
Diffstat (limited to 'arch/x86')
0 files changed, 0 insertions, 0 deletions