ath9k: fix reporting calculated new FFT upper max
authorSimon Wunderlich <sw@simonwunderlich.de>
Mon, 1 Oct 2018 14:26:59 +0000 (17:26 +0300)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Mon, 25 Nov 2019 08:53:22 +0000 (09:53 +0100)
[ Upstream commit 4fb5837ac2bd46a85620b297002c704e9958f64d ]

Since the debug print code is outside of the loop, it shouldn't use the loop
iterator anymore but instead print the found maximum index.

Cc: Nick Kossifidis <mickflemm@gmail.com>
Signed-off-by: Simon Wunderlich <sw@simonwunderlich.de>
Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
drivers/net/wireless/ath/ath9k/common-spectral.c

index eedf86b67cf517f4b9a400333cbc000ad28441d7..807fbe31e93039bbaca6465e7fd987eb18f55eff 100644 (file)
@@ -411,7 +411,7 @@ ath_cmn_process_ht20_40_fft(struct ath_rx_status *rs,
 
                ath_dbg(common, SPECTRAL_SCAN,
                        "Calculated new upper max 0x%X at %i\n",
-                       tmp_mag, i);
+                       tmp_mag, fft_sample_40.upper_max_index);
        } else
        for (i = dc_pos; i < SPECTRAL_HT20_40_NUM_BINS; i++) {
                if (fft_sample_40.data[i] == (upper_mag >> max_exp))