From: mabbas <mabbas@linux.intel.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Michael Wu <flamingice@sourmilk.net>,
linux-wireless@vger.kernel.org,
Jouni Malinen <jkm@devicescape.com>
Subject: Re: [patch 2/5] Add basic support for IEEE 802.11n discovery and association
Date: Wed, 11 Apr 2007 13:04:24 -0700 [thread overview]
Message-ID: <461D3F48.70004@linux.intel.com> (raw)
In-Reply-To: <20070411194059.GA2436@tuxdriver.com>
John W. Linville wrote:
> On Sat, Mar 31, 2007 at 11:37:19AM -0400, Michael Wu wrote:
>
>> On Monday 26 March 2007 07:38, mohamed wrote:
>>
>>> Add basic support for IEEE 802.11n discovery and association.
>>>
>>> This patch adds support to discover IEEE 802.11n AP and enable
>>> association to 802.11n Network. It parses beacon to discover 802.11n
>>> IE and include HT capability information element in Association Request
>>> Frame.
>>> It also call low level driver with the HT capability available during
>>> association.
>>>
>>>
>> So.. what happens when the user is using a userspace mlme?
>>
I am not familiar with userspace mlme what needed to be done?
Mohamed
>
> So...Michael is unhappy that I merged this one (and maybe unhappy
> about the whole series).
>
> Mohamed, could you address his concern that your patch preclude
> userland MLME functionality? Let's make sure we aren't closing-off
> that capability.
>
> Thanks,
>
> John
>
next prev parent reply other threads:[~2007-04-11 20:04 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 11:38 [patch 2/5] Add basic support for IEEE 802.11n discovery and association mohamed
2007-03-26 23:52 ` Randy Dunlap
2007-04-04 10:37 ` mabbas
2007-03-27 17:05 ` Luis R. Rodriguez
2007-03-27 17:11 ` Luis R. Rodriguez
2007-03-27 17:29 ` Luis R. Rodriguez
2007-03-29 6:04 ` mohamed
2007-03-28 19:11 ` Luis R. Rodriguez
2007-03-29 7:21 ` mohamed
2007-03-28 9:14 ` Johannes Berg
2007-03-29 5:56 ` mohamed
2007-03-28 20:03 ` Johannes Berg
2007-03-29 19:46 ` Luis R. Rodriguez
[not found] ` <1ba2fa240703291648h6b0d10bdje2ea54f3c1754f5b@mail.gmail.com>
2007-03-30 10:38 ` Johannes Berg
[not found] ` <1ba2fa240703300418r781931cdp50430dcb02259f1@mail.gmail.com>
2007-03-30 12:11 ` Johannes Berg
2007-03-31 15:37 ` Michael Wu
2007-04-11 19:40 ` John W. Linville
2007-04-11 20:04 ` mabbas [this message]
2007-04-11 20:29 ` Michael Wu
2007-04-11 22:03 ` Tomas Winkler
2007-04-11 22:50 ` Simon Barber
2007-04-11 23:05 ` Tomas Winkler
2007-04-11 23:25 ` Andy Green
2007-04-12 8:56 ` Johannes Berg
2007-04-12 9:01 ` Andy Green
2007-04-12 9:06 ` Johannes Berg
2007-04-12 0:20 ` Simon Barber
2007-04-12 1:13 ` Tomas Winkler
2007-04-11 22:23 ` mabbas
2007-04-11 22:56 ` Michael Wu
2007-04-12 18:11 ` mabbas
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=461D3F48.70004@linux.intel.com \
--to=mabbas@linux.intel.com \
--cc=flamingice@sourmilk.net \
--cc=jkm@devicescape.com \
--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;
as well as URLs for NNTP newsgroup(s).