Return-path: Received: from mms3.broadcom.com ([216.31.210.19]:4523 "EHLO MMS3.broadcom.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751295Ab1LPKDu (ORCPT ); Fri, 16 Dec 2011 05:03:50 -0500 Message-ID: <4EEB177A.603@broadcom.com> (sfid-20111216_110355_889501_5E71D126) Date: Fri, 16 Dec 2011 11:03:38 +0100 From: "Arend van Spriel" MIME-Version: 1.0 To: "Daniel Baluta" cc: "linux-wireless@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: unexpected taint message References: <4EEB0EFC.5000302@broadcom.com> In-Reply-To: Content-Type: text/plain; charset=iso-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: On 12/16/2011 10:29 AM, Daniel Baluta wrote: > Hello, > > On Fri, Dec 16, 2011 at 11:27 AM, 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. > > Is your driver GPL licensed? > > thanks, > Daniel. > Not entirely: MODULE_LICENSE("Dual BSD/GPL"); Gr. AvS