From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Subject: [RFC 3/4] mac80211: remove set_key_idx callback
Date: Wed, 22 Aug 2007 11:36:05 +0200 [thread overview]
Message-ID: <20070822093635.263993000@sipsolutions.net> (raw)
In-Reply-To: 20070822093602.028331000@sipsolutions.net
No existing drivers use this callback, hence there's no telling
how it might be used. In fact, it is unlikely to be of much use
as-is because the default key index isn't something that the
driver can do much with without knowing which interface it was
for etc. And if it needs the key index for the transmitted frame,
it can get it by keeping a reference to the key_conf structure
and looking it up by hw_key_idx.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
---
include/net/mac80211.h | 13 -------------
net/mac80211/key.c | 4 ----
2 files changed, 17 deletions(-)
--- wireless-dev.orig/include/net/mac80211.h 2007-08-22 10:26:14.879500061 +0200
+++ wireless-dev/include/net/mac80211.h 2007-08-22 10:26:54.429500061 +0200
@@ -733,19 +733,6 @@ struct ieee80211_ops {
const u8 *local_address, const u8 *address,
struct ieee80211_key_conf *key);
- /*
- * Set TX key index for default/broadcast keys. This is needed in cases
- * where wlan card is doing full WEP/TKIP encapsulation (wep_include_iv
- * is not set), in other cases, this function pointer can be set to
- * NULL since the IEEE 802.11 module takes care of selecting the key
- * index for each TX frame.
- *
- * TODO: If you use this callback in your driver tell us if you need
- * any other information from it to make it easier, like the
- * key_conf instead.
- */
- int (*set_key_idx)(struct ieee80211_hw *hw, int idx);
-
/* Enable/disable IEEE 802.1X. This item requests wlan card to pass
* unencrypted EAPOL-Key frames even when encryption is configured.
* If the wlan card does not require such a configuration, this
--- wireless-dev.orig/net/mac80211/key.c 2007-08-22 10:19:21.489500061 +0200
+++ wireless-dev/net/mac80211/key.c 2007-08-22 10:26:54.429500061 +0200
@@ -264,10 +264,6 @@ void ieee80211_set_default_key(struct ie
if (sdata->default_key)
ieee80211_debugfs_key_add_default(sdata);
-
- if (sdata->local->ops->set_key_idx)
- sdata->local->ops->set_key_idx(
- local_to_hw(sdata->local), idx);
}
}
--
next prev parent reply other threads:[~2007-08-22 9:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 9:36 [RFC 0/4] more hwcrypto/crypto cleanups + docs Johannes Berg
2007-08-22 9:36 ` [RFC 1/4] mac80211: rework hardware crypto flags Johannes Berg
2007-08-22 9:36 ` [RFC 2/4] mac80211: remove TKIP mixing for hw accel again Johannes Berg
2007-08-22 9:36 ` Johannes Berg [this message]
2007-08-22 9:36 ` [RFC 4/4] mac80211: some more documentation 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=20070822093635.263993000@sipsolutions.net \
--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;
as well as URLs for NNTP newsgroup(s).