wil6210: avoid dmesg pollution by Tx errors
On Tx path, when vring for the destination not found, it was considered as error and message was printed unconditionally. However, this situation is normal after disconnect. If disconnect was while heavy traffic load, lots of Tx packets will be dropped and this would cause significant amount of prints in dmesg. Demote messages priority from 'error' to 'debug'. Change-Id: I73c98b6b7c5af59eb70f1dc69aa859d47b7ec27f Signed-off-by:Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com> Signed-off-by:
John W. Linville <linville@tuxdriver.com> Git-commit: 5aed13932a36a4c12aad4d84b98d439f5b7af34e Git-repo: git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-testing.git Signed-off-by:
Hamad Kadmany <hkadmany@codeaurora.org>
Loading
Please register or sign in to comment