staging: wlan-ng: remove volatile from reapable field in hfa384x_usbctlx
authorTim Collier <osdevtc@gmail.com>
Wed, 25 Jul 2018 19:30:31 +0000 (20:30 +0100)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sun, 29 Jul 2018 08:08:02 +0000 (10:08 +0200)
commit318c66d456b81ce15b5e17b551d7db6ecc4aeac6
treeb0de75a1c02fe625a0755ac6a70957831b5983df
parentd3094361a91f21a5b6092b4d50c47be570ae02cf
staging: wlan-ng: remove volatile from reapable field in hfa384x_usbctlx

Fix checkpatch.pl warning:

"Use of volatile is usually wrong: see
Documentation/process/volatile-considered-harmful.rs"

reapable is not used to access h/w directly, so volatile is not
necessary.

>From reading the code, the contexts in which the field may be
updated/accessed across threads are protected by the hw->ctlxq.lock
spinlock, where hw is the device struct, so appears thread-safe.

Signed-off-by: Tim Collier <osdevtc@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/staging/wlan-ng/hfa384x.h