ath9k_hw: fix potential spurious tx error bit interpretation

According to documentation, AR_ExcessiveRetries, AR_Filtered and
AR_FIFOUnderrun are only valid if AR_FrmXmitOK is clear.

Not checking this might result in suboptimal FIFO settings, unnecessary
retransmissions, or other connectivity issues.
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
Cc: stable@kernel.org
Signed-off-by: John W. Linville <linville@tuxdriver.com>

drivers/net/wireless/ath/ath9k/ar9002_mac.c

@@ -237,6 +237,7 @@ static int ar9002_hw_proc_txdesc(struct ath_hw *ah, void *ds,
 	status = ACCESS_ONCE(ads->ds_txstatus1);
 	if (status & AR_FrmXmitOK)
 		ts->ts_status |= ATH9K_TX_ACKED;
+	else {
 		if (status & AR_ExcessiveRetries)
 			ts->ts_status |= ATH9K_TXERR_XRETRY;
 		if (status & AR_Filtered)
@@ -245,6 +246,7 @@ static int ar9002_hw_proc_txdesc(struct ath_hw *ah, void *ds,
 			ts->ts_status |= ATH9K_TXERR_FIFO;
 			ath9k_hw_updatetxtriglevel(ah, true);
 		}
+	}
 	if (status & AR_TxTimerExpired)
 		ts->ts_status |= ATH9K_TXERR_TIMER_EXPIRED;
 	if (status & AR_DescCfgErr)