| commit | 98aff6c005e322f2bd4a91ae2f3b3be3b8193d9b | |
| author | Wright Feng <wright.feng@broadcom.com> | |
| Fri, 3 Jun 2016 21:31:11 +0000 (3 23:31 +0200) | ||
| committer | Kalle Valo <kvalo@codeaurora.org> | |
| Thu, 16 Jun 2016 15:20:10 +0000 (16 18:20 +0300) | ||
| tree | 20f160fa8ca0347a725899fc025d5aa8c7bbf6ac | treesnapshot (tar.gz zip) |
| parent | 43819926eda54c38f31ce6175f3edf6c2987ceac | commitdiff |
brcmfmac: change rx_seq check log from error print to debug print
The bus rx sequence is not in order because that control and event
frames always cause immediate send, but data frames may be held
for glomming in firmware side. It is not actually an error as the
packets are still processed even if the RX sequence is not in order.
Therefor the error message is rephrased and changed to a debug
message.
Reviewed-by: Arend Van Spriel <arend@broadcom.com>
Signed-off-by: Wright Feng <wright.feng@broadcom.com>
Signed-off-by: Arend van Spriel <arend.vanspriel@broadcom.com>
Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
The bus rx sequence is not in order because that control and event
frames always cause immediate send, but data frames may be held
for glomming in firmware side. It is not actually an error as the
packets are still processed even if the RX sequence is not in order.
Therefor the error message is rephrased and changed to a debug
message.
Reviewed-by: Arend Van Spriel <arend@broadcom.com>
Signed-off-by: Wright Feng <wright.feng@broadcom.com>
Signed-off-by: Arend van Spriel <arend.vanspriel@broadcom.com>
Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
| drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c | diffblobblamehistory |