wil6210: use print_hex_dump_debug instead of print_hex_dump_bytes
authorDedy Lansky <qca_dlansky@qca.qualcomm.com>
Wed, 8 Mar 2017 11:52:13 +0000 (13:52 +0200)
committerKalle Valo <kvalo@qca.qualcomm.com>
Thu, 9 Mar 2017 08:04:14 +0000 (10:04 +0200)
commit5eb443e9af87776f94e77a9b72e54ceb81cbabc1
tree6fc4bbac759e63aad46f6af4ec09b85c0a3698bd
parent9953a782f9fac1becccb8f48f1a276c310f2ab5a
wil6210: use print_hex_dump_debug instead of print_hex_dump_bytes

Some dynamic debug printouts in driver are using print_hex_dump_bytes.
However, with dynamic debug disabled, print_hex_dump_bytes outputs to
log unconditionally.
Use print_hex_dump_debug instead to prevent log pollution when dynamic
debug disabled.

Signed-off-by: Dedy Lansky <qca_dlansky@qca.qualcomm.com>
Signed-off-by: Maya Erez <qca_merez@qca.qualcomm.com>
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
drivers/net/wireless/ath/wil6210/cfg80211.c
drivers/net/wireless/ath/wil6210/wil6210.h