Messages in this thread | | | Date | Fri, 16 Dec 2011 11:29:45 +0200 | Subject | Re: unexpected taint message | From | Daniel Baluta <> |
| |
Hello,
On Fri, Dec 16, 2011 at 11:27 AM, Arend van Spriel <arend@broadcom.com> 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.
Is your driver GPL licensed?
thanks, Daniel. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |