From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless <linux-wireless@vger.kernel.org>
Subject: notifications in nl80211
Date: Wed, 20 Jun 2007 11:19:47 +0200 [thread overview]
Message-ID: <1182331187.3714.28.camel@johannes.berg> (raw)
[-- Attachment #1: Type: text/plain, Size: 908 bytes --]
Hi,
After the previous two mails it seems that of the notifications we
currently send out, only these are left to implement in nl80211:
* ieee80211_msg_wep_frame_unknown_key
low priority, makes sense but isn't used in hostapd/wpasupplicant
* ieee80211_msg_key_threshold_notification
low priority, makes sense but isn't used in hostapd/wpasupplicant
* ieee80211_msg_michael_mic_failure
so really there's only one. All the others we can just delete (well, see
the other two mails), and these
* ieee80211_msg_normal
* ieee80211_msg_tx_callback_ack
* ieee80211_msg_tx_callback_fail
* ieee80211_msg_sta_not_assoc
* ieee80211_msg_passive_scan [completely unused]
are not useful when we mirror back packets to monitor mode interfaces on
tx status callback. That should actually be fairly easy to accomplish,
and then we can drop management interfaces completely.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
reply other threads:[~2007-06-20 11:17 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=1182331187.3714.28.camel@johannes.berg \
--to=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