From: Jon Masters <jonathan@jonmasters.org>
To: Brett Rudley <brudley@broadcom.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Henry Ptasinski <henryp@broadcom.com>,
Nohee Ko <noheek@broadcom.com>, Jon Masters <jcm@jonmasters.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: RE: PROBLEM: brcm80211 hangs on 2.6.36-0.34.rc6.git3.fc15.x86_64
Date: Mon, 11 Oct 2010 22:22:10 -0400 [thread overview]
Message-ID: <1286850130.30797.2.camel@constitution.bos.jonmasters.org> (raw)
In-Reply-To: <7A94256FD72B884D9E7C55586C3CBCEE1382807E23@SJEXCHCCR01.corp.ad.broadcom.com>
On Mon, 2010-10-11 at 14:01 -0700, Brett Rudley wrote:
> > Yea. What about the high order bits in the phy msglevel, what are they
> > intended to be doing?
>
> Nothing special, wl_msg_level is a standard bitmap, each bit enables printfs
> for a particular feature. There is no special meaning attached to the
> location an individual bit within the word.
Good to know, I had interpreted it as having a different meaning.
> Yeah, it would be less confusing if they were redefined to be more compact,
> I'll fix that up.
No biggie. Thanks.
Jon.
next prev parent reply other threads:[~2010-10-12 2:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 6:58 PROBLEM: brcm80211 hangs on 2.6.36-0.34.rc6.git3.fc15.x86_64 Jon Masters
2010-10-08 11:44 ` Jon Masters
2010-10-08 17:45 ` Brett Rudley
2010-10-11 20:12 ` Jon Masters
2010-10-11 21:01 ` Brett Rudley
2010-10-12 2:22 ` Jon Masters [this message]
2010-10-12 7:47 ` Jon Masters
2010-10-12 8:03 ` Jon Masters
2010-10-12 8:11 ` PROBLEM: brcm80211 hangs on 2.6.36-0.34.rc6.git3.fc15.x86_64 [FIXED] Jon Masters
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=1286850130.30797.2.camel@constitution.bos.jonmasters.org \
--to=jonathan@jonmasters.org \
--cc=brudley@broadcom.com \
--cc=henryp@broadcom.com \
--cc=jcm@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=noheek@broadcom.com \
/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