From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/9] cfg80211 spring cleaning
Date: Sat, 25 May 2013 00:01:21 +0200 [thread overview]
Message-ID: <1369432881.13623.13.camel@johannes> (raw)
In-Reply-To: <1368738218-7597-1-git-send-email-johannes@sipsolutions.net> (sfid-20130516_230344_782376_FD5FAA84)
On Thu, 2013-05-16 at 23:03 +0200, Johannes Berg wrote:
> Motivated by the bugs Ben Greear keeps reporting, I decided to do
> some locking and general cleanup in cfg80211.
>
> This is the first series. I'm working on more changes to actually
> separate the SME and MLME code much better to avoid such strange
> issues as we had before with their state (sme_state and current_bss)
> getting confused, but that'll take a bit longer.
Applied.
johannes
prev parent reply other threads:[~2013-05-24 22:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 21:03 [PATCH 0/9] cfg80211 spring cleaning Johannes Berg
2013-05-16 21:03 ` [PATCH 1/9] cfg80211: move cfg80211_get_dev_from_ifindex under wext Johannes Berg
2013-05-16 21:03 ` [PATCH 2/9] cfg80211: use atomic_t for wiphy counter Johannes Berg
2013-05-16 21:03 ` [PATCH 3/9] cfg80211: vastly simplify locking Johannes Berg
2013-05-16 21:03 ` [PATCH 4/9] cfg80211/mac80211: use cfg80211 wdev mutex in mac80211 Johannes Berg
2013-05-16 21:03 ` [PATCH 5/9] cfg80211: simplify and correct P2P-Device scan check Johannes Berg
2013-05-16 21:03 ` [PATCH 6/9] regulatory: use RCU in regulatory_hint_11d() Johannes Berg
2013-05-16 21:03 ` [PATCH 7/9] regulatory: remove reg_mutex Johannes Berg
2013-05-16 21:03 ` [PATCH 8/9] cfg80211: remove some locked wrappers from mlme API Johannes Berg
2013-05-16 21:03 ` [PATCH 9/9] cfg80211: remove some locked wrappers from sme API Johannes Berg
2013-05-24 22:01 ` Johannes Berg [this message]
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=1369432881.13623.13.camel@johannes \
--to=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