From: Johannes Berg <johannes@sipsolutions.net>
To: Zhu Yi <yi.zhu@intel.com>
Cc: Jouni Malinen <j@w1.fi>,
"hostap@lists.shmoo.com" <hostap@lists.shmoo.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Samuel Ortiz <sameo@linux.intel.com>
Subject: Re: [PATCH] nl80211 connect API support
Date: Fri, 14 Aug 2009 07:50:46 +0200 [thread overview]
Message-ID: <1250229046.7696.0.camel@johannes.local> (raw)
In-Reply-To: <1250223474.4972.47.camel@debian>
[-- Attachment #1: Type: text/plain, Size: 733 bytes --]
On Fri, 2009-08-14 at 12:17 +0800, Zhu Yi wrote:
> Johannes, I think we need a way in cfg80211 to tell connect vs.
> auth/assoc. The current capability method (nl80211_send_wiphy) cannot do
> this. For example,
>
> if (dev->ops->connect || dev->ops->auth)
> NLA_PUT_U32(msg, i, NL80211_CMD_CONNECT);
>
> We need to either make NL80211_CMD_CONNECT only depends on ops->connect
> or make NL80211_CMD_AUTH depends on ops->auth. Johannes, which one do
> you prefer?
The latter is already there as far as I can see?
CMD(auth, AUTHENTICATE);
CMD(assoc, ASSOCIATE);
CMD(deauth, DEAUTHENTICATE);
CMD(disassoc, DISASSOCIATE);
so you should be able to check for these.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-08-14 5:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 8:55 [PATCH] Fix cipher overwide problem for 802.1X WEP Zhu Yi
2009-08-13 8:55 ` [PATCH] nl80211 connect API support Zhu Yi
2009-08-13 9:11 ` Jouni Malinen
2009-08-13 9:29 ` Zhu Yi
2009-08-13 10:46 ` Jouni Malinen
2009-08-14 4:17 ` Zhu Yi
2009-08-14 5:50 ` Johannes Berg [this message]
2009-08-14 7:55 ` Zhu Yi
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=1250229046.7696.0.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=hostap@lists.shmoo.com \
--cc=j@w1.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=sameo@linux.intel.com \
--cc=yi.zhu@intel.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;
as well as URLs for NNTP newsgroup(s).