From: Johannes Berg <johannes@sipsolutions.net>
To: John Linville <linville@tuxdriver.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: [PATCH] mac80211: improve sta_notify documentation
Date: Mon, 08 Dec 2008 11:18:32 +0100 [thread overview]
Message-ID: <1228731512.22164.72.camel@johannes.berg> (raw)
Mention more possible STA entries and document the atomic requirement.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
---
include/net/mac80211.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- everything.orig/include/net/mac80211.h 2008-12-08 11:16:25.000000000 +0100
+++ everything/include/net/mac80211.h 2008-12-08 11:17:24.000000000 +0100
@@ -1257,8 +1257,8 @@ enum ieee80211_ampdu_mlme_action {
* the device does fragmentation by itself; if this method is assigned then
* the stack will not do fragmentation.
*
- * @sta_notify: Notifies low level driver about addition or removal
- * of associated station or AP.
+ * @sta_notify: Notifies low level driver about addition or removal of an
+ * associated station, AP, IBSS/WDS/mesh peer etc. Must be atomic.
*
* @sta_ps_notify: Notifies low level driver about the power state transition
* of a associated station. Must be atomic.
reply other threads:[~2008-12-08 13:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1228731512.22164.72.camel@johannes.berg \
--to=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