From: Johannes Berg <johannes@sipsolutions.net>
To: Masakazu Mokuno <mokuno@sm.sony.co.jp>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/3] RFC: Add support for passing PMK to WEXT
Date: Sat, 26 Apr 2008 18:13:47 +0200 [thread overview]
Message-ID: <1209226427.10943.47.camel@johannes.berg> (raw)
In-Reply-To: <20080424204950.03DD.40F06B3A@sm.sony.co.jp> (sfid-20080425_065439_493690_DC304A3E)
[-- Attachment #1: Type: text/plain, Size: 664 bytes --]
Hi,
> - define the standard way to pass the PMK to the driver
> - let user space programs figure out whether the driver will do 4-way
> handshakes
> - eliminate the use of private ioctls from the gelic driver
>
> #1 Add support for passing PMK and capability flags to WEXT
> #2 Use the new PMK interface in the gelic driver
> #3 Deprecate the private ioctls in the gelic driver
>
>
> #1 adds the flags to WEXT, #2 and #3 let the gelic driver conform.
>
> Please review!
Looks fine to me. You might want to ask for Jouni's input since took
part in the original design and will have to take the wpa_supplicant
patch :)
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2008-04-26 16:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-25 4:51 [PATCH 0/3] RFC: Add support for passing PMK to WEXT Masakazu Mokuno
2008-04-25 5:05 ` [PATCH 2/3] RFC: PS3: gelic: Use the new PMK interface in the gelic driver Masakazu Mokuno
2008-04-25 5:05 ` [PATCH 1/3] RFC: WEXT: Add support for passing PMK and capability flags to WEXT Masakazu Mokuno
2008-04-25 5:05 ` [PATCH 3/3] RFC: PS3: gelic: Deprecate the private ioctls in the gelic driver Masakazu Mokuno
2008-04-26 16:13 ` Johannes Berg [this message]
2008-04-27 6:35 ` [PATCH 0/3] RFC: Add support for passing PMK to WEXT Jouni Malinen
2008-04-28 4:07 ` Dan Williams
2008-05-07 10:06 ` Masakazu Mokuno
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=1209226427.10943.47.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mokuno@sm.sony.co.jp \
/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).