orinoco: clear countermeasure setting on commit
authorDavid Kilroy <kilroyd@googlemail.com>
Sun, 5 Dec 2010 15:45:58 +0000 (15:45 +0000)
committerJohn W. Linville <linville@tuxdriver.com>
Wed, 8 Dec 2010 20:23:52 +0000 (15:23 -0500)
commitba34fcee476d11e7c9df95932787a22a96ff6e68
treed0c15f9adb8a36f103d397c2d1b759418b8c5513
parent7e2447075690860e2cea96b119fc9cadbaa7e83c
orinoco: clear countermeasure setting on commit

... 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>
Cc: stable@kernel.org
Signed-off-by: John W. Linville <linville@tuxdriver.com>
drivers/net/wireless/orinoco/main.c