From: "Arend van Spriel" <arend@broadcom.com>
To: "Daniel Baluta" <daniel.baluta@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: unexpected taint message
Date: Fri, 16 Dec 2011 11:03:38 +0100 [thread overview]
Message-ID: <4EEB177A.603@broadcom.com> (raw)
In-Reply-To: <CAEnQRZA+Om=1VKpRQiSxvRzvkbicmsR=wsyskFu-WQ8HrbuM4Q@mail.gmail.com>
On 12/16/2011 10:29 AM, Daniel Baluta wrote:
> 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.
>
Not entirely:
MODULE_LICENSE("Dual BSD/GPL");
Gr. AvS
next prev parent reply other threads:[~2011-12-16 10:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 9:27 unexpected taint message Arend van Spriel
2011-12-16 9:29 ` Daniel Baluta
2011-12-16 10:03 ` Arend van Spriel [this message]
2011-12-16 12:30 ` Johannes Berg
2011-12-16 13:53 ` Larry Finger
2011-12-16 13:58 ` Johannes Berg
2011-12-16 14:13 ` Larry Finger
2011-12-16 14:20 ` Johannes Berg
2011-12-16 14:49 ` Larry Finger
2011-12-16 14:51 ` Johannes Berg
2011-12-16 14:48 ` Nick Bowler
2011-12-16 14:57 ` Larry Finger
2011-12-16 14:58 ` Johannes Berg
2011-12-16 14:00 ` Arend van Spriel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EEB177A.603@broadcom.com \
--to=arend@broadcom.com \
--cc=daniel.baluta@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.