From: "Arend van Spriel" <arend@broadcom.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, greearb@candelatech.com,
"Johannes Berg" <johannes.berg@intel.com>
Subject: Re: [RFC 4/4] cfg80211/mac80211: use cfg80211 wdev mutex in mac80211
Date: Fri, 10 May 2013 14:22:27 +0200 [thread overview]
Message-ID: <518CE683.2040402@broadcom.com> (raw)
In-Reply-To: <1368187689-29706-5-git-send-email-johannes@sipsolutions.net>
On 05/10/2013 02:08 PM, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> Using separate locks in cfg80211 and mac80211 has always
> caused issues, for example having to unlock in places in
> mac80211 to call cfg80211, which even needed a framework
> to make cfg80211 calls after some functions returned etc.
>
> Additionally, I suspect some issues people have reported
> with the cfg80211 state getting confused could be due to
> such issues, when cfg80211 is asking mac80211 to change
> state but mac80211 is in the process of telling cfg80211
> that the state changed (in another way.)
I guess this change affects fullmac drivers like brcmfmac, right?
Gr. AvS
next prev parent reply other threads:[~2013-05-10 12:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 12:08 [RFC 0/4] cfg80211/mac80211: simplify locking Johannes Berg
2013-05-10 12:08 ` [RFC 1/4] cfg80211: move cfg80211_get_dev_from_ifindex under wext Johannes Berg
2013-05-10 12:08 ` [RFC 2/4] cfg80211: use atomic_t for wiphy counter Johannes Berg
2013-05-10 12:08 ` [RFC 3/4] cfg80211: vastly simplify locking Johannes Berg
2013-05-10 12:08 ` [RFC 4/4] cfg80211/mac80211: use cfg80211 wdev mutex in mac80211 Johannes Berg
2013-05-10 12:22 ` Arend van Spriel [this message]
2013-05-10 12:26 ` Johannes Berg
2013-05-11 16:19 ` Arend van Spriel
2013-05-13 7:09 ` Johannes Berg
2013-05-10 12:09 ` [RFC 0/4] cfg80211/mac80211: simplify locking Johannes Berg
2013-05-10 14:26 ` Ben Greear
2013-05-10 14:27 ` 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=518CE683.2040402@broadcom.com \
--to=arend@broadcom.com \
--cc=greearb@candelatech.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).