Return-path: <linux-wireless-owner@vger.kernel.org>
Received: from mms1.broadcom.com ([216.31.210.17]:3720 "EHLO mms1.broadcom.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752149Ab3EJMWq (ORCPT <rfc822;linux-wireless@vger.kernel.org>);
	Fri, 10 May 2013 08:22:46 -0400
Message-ID: <518CE683.2040402@broadcom.com> (sfid-20130510_142249_383263_5C34BF35)
Date: Fri, 10 May 2013 14:22:27 +0200
From: "Arend van Spriel" <arend@broadcom.com>
MIME-Version: 1.0
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
References: <1368187689-29706-1-git-send-email-johannes@sipsolutions.net>
 <1368187689-29706-5-git-send-email-johannes@sipsolutions.net>
In-Reply-To: <1368187689-29706-5-git-send-email-johannes@sipsolutions.net>
Content-Type: text/plain;
 charset=iso-8859-1;
 format=flowed
Sender: linux-wireless-owner@vger.kernel.org
List-ID: <linux-wireless.vger.kernel.org>

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