From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC 0/4] cfg80211/mac80211: simplify locking
Date: Fri, 10 May 2013 07:26:24 -0700 [thread overview]
Message-ID: <518D0390.90006@candelatech.com> (raw)
In-Reply-To: <1368187689-29706-1-git-send-email-johannes@sipsolutions.net>
On 05/10/2013 05:08 AM, Johannes Berg wrote:
> I got a little fed up with all the locking, and decided to simplify.
>
> This should still work, but I've only done some very simple tests.
> I'm hoping it'll fix some of the weird corner cases that Ben and
> others have found, which may be due to different locks in different
> cases and things racing against each other ... I'm not convinced it
> really will though, but hey, who knows :)
I'm stacked high with tasks at the moment, but will try to
run this through some testing soon.
These are in your tree?
Thanks,
Ben
>
> johannes
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2013-05-10 14:26 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
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 [this message]
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=518D0390.90006@candelatech.com \
--to=greearb@candelatech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.