From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/2] cfg80211: decouple regulatory variables from cfg80211_mutex
Date: Thu, 30 Jul 2009 07:54:41 -0700 [thread overview]
Message-ID: <43e72e890907300754v7ed8cb66w9b1bdbfe9917486c@mail.gmail.com> (raw)
In-Reply-To: <1248939781.8925.2.camel@johannes.local>
On Thu, Jul 30, 2009 at 12:43 AM, Johannes
Berg<johannes@sipsolutions.net> wrote:
> On Wed, 2009-07-29 at 17:46 -0700, Luis R. Rodriguez wrote:
>> We change regulatory code to be protected by its own regulatory
>> spinlock and alleviate cfg80211_mutex to only be used to protect
>> cfg80211_rdev_list, the registered device list.
>>
>> By doing this we will be able to work on regulatory core components
>> without having to have hog up the cfg80211_mutex. An example here is
>> we no longer need to use the cfg80211_mutex during the country IE
>> regulatory hint; by doing so we end up curing this new lockdep warning:
>
> This is ok with me, but be sure that it changes the API between drivers
> and cfg80211 -- the reg notifier can no longer sleep now.
We could use a mutex as well.
Luis
next prev parent reply other threads:[~2009-07-30 14:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 0:46 [PATCH 0/2] wireless: fix 11d lockdep warning Luis R. Rodriguez
2009-07-30 0:46 ` [PATCH 1/2] cfg80211: use goto out on 11d reg hint failure Luis R. Rodriguez
2009-07-30 0:46 ` [PATCH 2/2] cfg80211: decouple regulatory variables from cfg80211_mutex Luis R. Rodriguez
2009-07-30 7:43 ` Johannes Berg
2009-07-30 14:54 ` Luis R. Rodriguez [this message]
2009-07-30 15:32 ` Johannes Berg
2009-07-30 15:34 ` Luis R. Rodriguez
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=43e72e890907300754v7ed8cb66w9b1bdbfe9917486c@mail.gmail.com \
--to=lrodriguez@atheros.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).