Tracing in wil6210 is activated with WIL6210_TRACING and not with
ATH6KL_TRACING, this is used for the ath6kl driver. Rename the config
option.
Signed-off-by: Hauke Mehrtens <[email protected]>
---
drivers/net/wireless/ath/wil6210/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wireless/ath/wil6210/Kconfig b/drivers/net/wireless/ath/wil6210/Kconfig
index 5644ac5..ce8c038 100644
--- a/drivers/net/wireless/ath/wil6210/Kconfig
+++ b/drivers/net/wireless/ath/wil6210/Kconfig
@@ -28,7 +28,7 @@ config WIL6210_ISR_COR
such monitoring impossible.
Say y unless you debug interrupts
-config ATH6KL_TRACING
+config WIL6210_TRACING
bool "wil6210 tracing support"
depends on WIL6210
depends on EVENT_TRACING
--
1.7.10.4
On Sunday, June 09, 2013 01:10:05 PM Hauke Mehrtens wrote:
> Tracing in wil6210 is activated with WIL6210_TRACING and not with
> ATH6KL_TRACING, this is used for the ath6kl driver. Rename the config
> option.
>
> Signed-off-by: Hauke Mehrtens <[email protected]>
Thanks for finding this.
Acked-by: Vladimir Kondratiev <[email protected]>