From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] lockdep: Don't disable lockdep for out of tree modules
Date: Wed, 16 Nov 2011 16:30:28 +0530 [thread overview]
Message-ID: <87obwcl4c3.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <1321433203.1421.69.camel@twins>
On Wed, 16 Nov 2011 09:46:43 +0100, Peter Zijlstra <peterz@infradead.org> wrote:
> On Wed, 2011-11-16 at 13:20 +0530, Aneesh Kumar K.V wrote:
> > From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
> >
> > I guess it would be nice to get lockdep enabled for out of tree GPL modules
>
> How about you get them in staging instead?
>
I actually wanted to do a sample module to demo lockdep in one of the
presentation i am doing and that is when i hit the issue. I don't have
a kernel module that i would like to keep out of tree. I am not sure
there is any value in disabling lockdep if one load an out of tree GPL
kernel module.
-aneesh
prev parent reply other threads:[~2011-11-16 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 7:50 [PATCH] lockdep: Don't disable lockdep for out of tree modules Aneesh Kumar K.V
2011-11-16 8:46 ` Peter Zijlstra
2011-11-16 11:00 ` Aneesh Kumar K.V [this message]
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=87obwcl4c3.fsf@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox