ath5k: use 3 instead of 0x00000003

reviewed beacon timer initialization with register traces from madwifi: what we
are doing is correct :). one minor fix: use 3 instead of 0x00000003 - it's more
readable.

drivers/net/wireless/ath5k/hw.c:        Changes-licensed-under: ISC

Signed-off-by: Bruno Randolf <bruno@thinktube.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>

1 files changed, 2 insertions, 4 deletions

diff --git a/drivers/net/wireless/ath5k/hw.c b/drivers/net/wireless/ath5k/hw.c
index eb00818e8ce6..3a4bf4035a23 100644
--- a/drivers/net/wireless/ath5k/hw.c
+++ b/drivers/net/wireless/ath5k/hw.c
@@ -2605,10 +2605,8 @@ void ath5k_hw_init_beacon(struct ath5k_hw *ah, u32 next_beacon, u32 interval)
                 break;
 
         default:
-                timer1 = (next_beacon - AR5K_TUNE_DMA_BEACON_RESP) <<
-                    0x00000003;
-                timer2 = (next_beacon - AR5K_TUNE_SW_BEACON_RESP) <<
-                    0x00000003;
+                timer1 = (next_beacon - AR5K_TUNE_DMA_BEACON_RESP) << 3;
+                timer2 = (next_beacon - AR5K_TUNE_SW_BEACON_RESP) << 3;
         }
 
         timer3 = next_beacon + (ah->ah_atim_window ? ah->ah_atim_window : 1);