summaryrefslogtreecommitdiffstats
path: root/drivers/net
diff options
context:
space:
mode:
authorBartosz Markowski <bartosz.markowski@tieto.com>2014-02-11 08:37:06 +0100
committerKalle Valo <kvalo@qca.qualcomm.com>2014-02-13 16:47:45 +0200
commit7c61385454b639a68e434496c1cae9ec4d98d99e (patch)
tree43c5b1f7eca23057fda9368333597ab25dc697cf /drivers/net
parent75fb2f94f2115a616c6066b55c35495482514608 (diff)
downloadlinux-stable-7c61385454b639a68e434496c1cae9ec4d98d99e.tar.gz
linux-stable-7c61385454b639a68e434496c1cae9ec4d98d99e.tar.bz2
linux-stable-7c61385454b639a68e434496c1cae9ec4d98d99e.zip
ath10k: remove excessive rx msdu len check
This throw a lot of pointless warnings in case of DFS (radar detection) and PHYERR events from firmware, when firmware may actually insert more data, than we assume. Besides of being noisy this debug does not protect or check anything usefull currently. It was introduced long time ago while debugging aggregations. So just removing it. Signed-off-by: Bartosz Markowski <bartosz.markowski@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
Diffstat (limited to 'drivers/net')
-rw-r--r--drivers/net/wireless/ath/ath10k/htt_rx.c6
1 files changed, 0 insertions, 6 deletions
diff --git a/drivers/net/wireless/ath/ath10k/htt_rx.c b/drivers/net/wireless/ath/ath10k/htt_rx.c
index 5d073d9afbbf..820c8ba3b1ec 100644
--- a/drivers/net/wireless/ath/ath10k/htt_rx.c
+++ b/drivers/net/wireless/ath/ath10k/htt_rx.c
@@ -430,12 +430,6 @@ static int ath10k_htt_rx_amsdu_pop(struct ath10k_htt *htt,
msdu_chaining = 1;
}
- if (msdu_len > 0) {
- /* This may suggest FW bug? */
- ath10k_warn("htt rx msdu len not consumed (%d)\n",
- msdu_len);
- }
-
last_msdu = __le32_to_cpu(rx_desc->msdu_end.info0) &
RX_MSDU_END_INFO0_LAST_MSDU;