From: Nick Bowler <nbowler@elliptictech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Arend van Spriel <arend@broadcom.com>,
"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 09:48:04 -0500 [thread overview]
Message-ID: <20111216144804.GA11693@elliptictech.com> (raw)
In-Reply-To: <1324043939.3429.2.camel@jlt3.sipsolutions.net>
On 2011-12-16 14:58 +0100, Johannes Berg wrote:
> Hmm. I wish OOT didn't disable lockdep, we do a lot of development with
> modules OOT because the turnaround is faster/easier (for not so
> experienced developers). Worst case we can patch it out of the base
> kernel I guess...
Indeed, but the good news is that we should finally be able to put this
issue behind us soon(ish).
https://git.kernel.org/?p=linux/kernel/git/tip/tip.git;a=commit;h=9ec84acee1e221d99dc33237bff5e82839d10cc0
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
next prev parent reply other threads:[~2011-12-16 14:57 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
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 [this message]
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=20111216144804.GA11693@elliptictech.com \
--to=nbowler@elliptictech.com \
--cc=Larry.Finger@lwfinger.net \
--cc=arend@broadcom.com \
--cc=johannes@sipsolutions.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).