From: Bob Copeland <me@bobcopeland.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, Johannes Berg <johannes.berg@intel.com>
Subject: Re: [RFC v2 14/18] regulatory: clarify locking rules and assertions
Date: Tue, 4 Dec 2012 14:07:30 -0500 [thread overview]
Message-ID: <20121204190730.GC29880@localhost> (raw)
In-Reply-To: <1354632540-21207-15-git-send-email-johannes@sipsolutions.net>
On Tue, Dec 04, 2012 at 03:48:56PM +0100, Johannes Berg wrote:
> Many places that currently check that cfg80211_
> The function needs to hold the cfg80211_mutex as
> it uses the global cfg80211_regdomain variable, so
> add the lock assertion to it and fix one of the
> callers that doesn't hold that mutex.
Something missing in the description there?
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2012-12-04 19:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-04 14:48 regulatory cleanups & fixes Johannes Berg
2012-12-04 14:48 ` [RFC v2 01/18] regulatory: don't allocate too much memory Johannes Berg
2012-12-04 14:48 ` [RFC v2 02/18] regulatory: clean up reg_copy_regd() Johannes Berg
2012-12-04 14:48 ` [RFC v2 03/18] regulatory: don't test list before iterating Johannes Berg
2012-12-04 14:48 ` [RFC v2 04/18] regulatory: simplify regulatory_hint_11d Johannes Berg
2012-12-04 14:48 ` [RFC v2 05/18] regulatory: code cleanup Johannes Berg
2012-12-04 14:48 ` [RFC v2 06/18] regulatory: remove useless locking on exit Johannes Berg
2012-12-04 14:48 ` [RFC v2 07/18] regulatory: use proper enum for return values Johannes Berg
2012-12-04 14:48 ` [RFC v2 08/18] cfg80211: remove wiphy_idx_valid Johannes Berg
2012-12-04 14:48 ` [RFC v2 09/18] regulatory: remove BUG_ON Johannes Berg
2012-12-04 14:48 ` [RFC v2 10/18] regulatory: simplify restore_regulatory_settings Johannes Berg
2012-12-04 14:48 ` [RFC v2 11/18] regulatory: remove redundant isalpha() check Johannes Berg
2012-12-04 14:48 ` [RFC v2 12/18] regulatory: remove useless warning Johannes Berg
2012-12-04 14:48 ` [RFC v2 13/18] regulatory: simplify freq_reg_info_regd Johannes Berg
2012-12-04 14:48 ` [RFC v2 14/18] regulatory: clarify locking rules and assertions Johannes Berg
2012-12-04 19:07 ` Bob Copeland [this message]
2012-12-05 9:13 ` Johannes Berg
2012-12-04 14:48 ` [RFC v2 15/18] regulatory: remove locking from wiphy_apply_custom_regulatory Johannes Berg
2012-12-04 14:48 ` [RFC v2 16/18] regulatory: fix reg_is_valid_request handling Johannes Berg
2012-12-04 14:48 ` [RFC v2 17/18] regulatory: remove handling of channel bandwidth Johannes Berg
2012-12-04 14:49 ` [RFC v2 18/18] regulatory: allow arbitrary channel widths Johannes Berg
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=20121204190730.GC29880@localhost \
--to=me@bobcopeland.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--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).