On Wed, 2012-03-21 at 21:29 -0700, Luis R. Rodriguez wrote: > But no dice. I then figured it may be my kernel with > CONFIG_TRACEPOINTS=y and indeed that is the case -- so we have to > consider the case where the target kernel may have tracing enabled and > we have to disable it somehow. Undef'ing CONFIG_TRACEPOINTS and > DECLARE_TRACE doesn't really do it. Oh, ok, yuck. So I guess we can't easily disable tracing if it's enabled in the base kernel ... > We may need to redefine each macro to some COMPAT_TRACE_ macro, not sure yet. That would require patches again though, no fun either. johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
