From: Zhu Yi <yi.zhu@intel.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 3/5] iwmc3200wifi: use cfg80211_connect_result to send req/resp IE
Date: Tue, 21 Jul 2009 09:22:14 +0800 [thread overview]
Message-ID: <1248139334.3747.22.camel@debian> (raw)
In-Reply-To: <1248086241.14765.1.camel@johannes.local>
On Mon, 2009-07-20 at 18:37 +0800, Johannes Berg wrote:
> On Mon, 2009-07-20 at 11:47 +0800, Zhu Yi wrote:
> > cfg80211_connect_result() let us specify associate request and
> > response IEs as parameters after we are connected. We use this
> > capability instead of doing it ourselves with WEXT.
>
> I think with this, you can now remove
>
> select WIRELESS_EXT
>
> from your Kconfig.
Um, not yet. I need to assign the netdev->wireless_handlers to
&iwm_iw_handler_def. The former is ifdef-ed CONFIG_WIRELESS_EXT in
struct net_device. I think this can be done until cdg80211 provides a
generic iw_handler.
Thanks,
-yi
next prev parent reply other threads:[~2009-07-21 1:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 3:47 [PATCH 00/0] iwmc3200wifi: fix WPA connect problem Zhu Yi
2009-07-20 3:47 ` [PATCH 1/5] cfg80211: set_default_key only for WEP Zhu Yi
2009-07-20 3:47 ` [PATCH 2/5] cfg80211: fix typo of IWEVASSOCRESPIE Zhu Yi
2009-07-20 3:47 ` [PATCH 3/5] iwmc3200wifi: use cfg80211_connect_result to send req/resp IE Zhu Yi
2009-07-20 3:47 ` [PATCH 4/5] iwmc3200wifi: fix cfg80211_connect_result is called in IBSS Zhu Yi
2009-07-20 3:47 ` [PATCH 5/5] iwmc3200wifi: fix a use-after-free bug Zhu Yi
2009-07-20 10:37 ` [PATCH 3/5] iwmc3200wifi: use cfg80211_connect_result to send req/resp IE Johannes Berg
2009-07-21 1:22 ` Zhu Yi [this message]
2009-07-21 10:50 ` Johannes Berg
2009-07-20 10:36 ` [PATCH 2/5] cfg80211: fix typo of IWEVASSOCRESPIE Johannes Berg
2009-07-20 10:34 ` [PATCH 1/5] cfg80211: set_default_key only for WEP 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=1248139334.3747.22.camel@debian \
--to=yi.zhu@intel.com \
--cc=johannes@sipsolutions.net \
--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).