[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4EEB177A.603@broadcom.com>
Date: Fri, 16 Dec 2011 11:03:38 +0100
From: "Arend van Spriel" <arend@...adcom.com>
To: "Daniel Baluta" <daniel.baluta@...il.com>
cc: "linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: unexpected taint message
On 12/16/2011 10:29 AM, Daniel Baluta wrote:
> Hello,
>
> On Fri, Dec 16, 2011 at 11:27 AM, Arend van Spriel <arend@...adcom.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.
>
Not entirely:
MODULE_LICENSE("Dual BSD/GPL");
Gr. AvS
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists