From: "John W. Linville" <linville@tuxdriver.com>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: WARNING: at kernel/lockdep.c:3151 check_flags+0x63/0x179()
Date: Tue, 8 Feb 2011 09:03:56 -0500 [thread overview]
Message-ID: <20110208140355.GA2448@tuxdriver.com> (raw)
In-Reply-To: <4D50BF6D.5050408@gmail.com>
On Mon, Feb 07, 2011 at 07:58:37PM -0800, Justin P. Mattock wrote:
> not sure if this is o.k. or not due to the message giving me a few
> messages(full dmesg below)
No idea, but it probably isn't good...the better question is what
made you send this to linux-wireless? Nothing in the stacktraces
seems to point at wireless stuff...
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2011-02-08 14:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 3:58 WARNING: at kernel/lockdep.c:3151 check_flags+0x63/0x179() Justin P. Mattock
2011-02-08 14:03 ` John W. Linville [this message]
2011-02-08 14:59 ` Justin Mattock
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=20110208140355.GA2448@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=justinmattock@gmail.com \
--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).