On Fri, 2011-12-16 at 10:27 +0100, Arend van Spriel wrote: > To whoever may know, > > Upon loading our driver module I get the following message: > > kernel: [ 344.805106] Disabling lock debugging due to kernel taint > > What exactly are the criteria for tainting? Our driver locking strategy > is something we want to refactor and having lock debugging during that > transition may be a life safer. cat /proc/sys/kernel/tainted 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
