From: "Arend van Spriel" <arend@broadcom.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "Josh Boyer" <jwboyer@redhat.com>,
"Johannes Berg" <johannes@sipsolutions.net>,
"Brett Rudley" <brudley@broadcom.com>,
"Roland Vossen" <rvossen@broadcom.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
"Seth Forshee" <seth.forshee@canonical.com>
Subject: Re: assert_cfg80211_lock warning with Linux v3.5-8833-g2d53492
Date: Wed, 1 Aug 2012 17:51:08 +0200 [thread overview]
Message-ID: <5019506C.6020707@broadcom.com> (raw)
In-Reply-To: <50194D7A.6060400@broadcom.com>
On 08/01/2012 05:38 PM, Arend van Spriel wrote:
>> brcmsmac needs to hold cfg80211_mutex before calling freq_reg_info...
>> >
>> > It looks like those calls were added in mid-June.
>> >
> I think mid-june sounds about right. We never observed the warning when
> changes to use regulatory infrastructure were tested/reviewed. Should
> this precondition be mentioned in cfg80211.h?
>
> Gr. AvS
Diving in further it seems brcmsmac can not grab the cfg80211_mutex. So
another solution is needed.
Gr. AvS
next prev parent reply other threads:[~2012-08-01 15:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 13:12 assert_cfg80211_lock warning with Linux v3.5-8833-g2d53492 Josh Boyer
2012-08-01 14:18 ` John W. Linville
2012-08-01 15:38 ` Arend van Spriel
2012-08-01 15:51 ` Arend van Spriel [this message]
2012-08-01 15:52 ` John W. Linville
2012-08-01 16:40 ` Arend van Spriel
2012-08-01 15:53 ` Johannes Berg
2012-08-01 16:19 ` Seth Forshee
2012-08-01 17:14 ` Johannes Berg
2012-08-01 17:56 ` Seth Forshee
2012-08-01 17:24 ` Arend van Spriel
2012-08-01 19:28 ` 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=5019506C.6020707@broadcom.com \
--to=arend@broadcom.com \
--cc=brudley@broadcom.com \
--cc=johannes@sipsolutions.net \
--cc=jwboyer@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=rvossen@broadcom.com \
--cc=seth.forshee@canonical.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;
as well as URLs for NNTP newsgroup(s).