From: Bob Copeland <me@bobcopeland.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: acquire sta_lock for station suspend/resume
Date: Sat, 14 Mar 2009 19:40:29 -0400 [thread overview]
Message-ID: <b6c5339f0903141640j6f0ef1e0rccb4034006c9ba1f@mail.gmail.com> (raw)
In-Reply-To: <1237020169.5235.66.camel@johannes.local>
On Sat, Mar 14, 2009 at 4:42 AM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> To avoid concurrent manipulations of the sta list (which shouldn't
> be possible at this point, but anyway) we need to hold the sta_lock
> around iterating the list.
>
> At the same time, we do not need to iterate the list at all if
> the driver doesn't want to be notified.
>
> Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Acked-by: Bob Copeland <me@bobcopeland.com>
--
Bob Copeland %% www.bobcopeland.com
prev parent reply other threads:[~2009-03-14 23:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-14 8:42 [PATCH] mac80211: acquire sta_lock for station suspend/resume Johannes Berg
2009-03-14 23:40 ` Bob Copeland [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=b6c5339f0903141640j6f0ef1e0rccb4034006c9ba1f@mail.gmail.com \
--to=me@bobcopeland.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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