Sujith Manoharan <[email protected]> writes: > Kalle Valo wrote: >> Why add it to ath.ko module? What drivers are going to use this? > > The debug code for ath9k is in ath.ko.
You mean ath_printk() & friends? But that doesn't require tracing code to be in ath.ko as well, right? If I understood correctly, trace.c could be under ath9k directory and the kconfig option could be ATH9K_TRACEPOINTS. I think it's just misleading and confusing for the user to call it "Atheros wireless tracing" when it only affects ath9k. It's easier to understand if each driver has it's own "tracing" kconfig option. -- Kalle Valo -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
