From: "Jouni Malinen" <jkm@devicescape.com>
To: Michael Wu <flamingice@sourmilk.net>
Cc: John Linville <linville@tuxdriver.com>, Jiri Benc <jbenc@suse.cz>,
netdev@vger.kernel.org
Subject: Re: [PATCH wireless-dev] d80211: Switch d80211_mgmt.h to ieee80211.h style definitions
Date: Mon, 7 Aug 2006 10:20:50 -0700 [thread overview]
Message-ID: <20060807172050.GH4702@instant802.com> (raw)
In-Reply-To: <200608050145.40137.flamingice@sourmilk.net>
On Sat, Aug 05, 2006 at 01:45:33AM -0700, Michael Wu wrote:
> d80211: Switch d80211_mgmt.h to ieee80211.h style definitions
>
> This patch switches a number of defines in d80211_mgmt.h to enums taken from
> ieee80211.h and makes the corresponding changes in net/d80211.
> include/net/d80211_mgmt.h | 153
> net/d80211/ieee80211.c | 2 -
> net/d80211/ieee80211_sta.c | 50 +++++++-------
Is this really needed? Based on the changes here, these are mostly used
internally in net/d80211/ieee80211_sta.c and not in other parts of the
tree. In addition, I would actually like to see ieee80211_sta.c be made
mostly obsolete with a user space implementation of client MLME (e.g.,
the one in wpa_supplicant which is based on this ieee80211_sta.c file).
Changing WLAN_STATUS_* and WLAN_REASON_* to be enum's while keeping
their old names is fine. However, I would rather not change the names of
the information element IDs (WLAN_EID_*) into MFIE_TYPE_*. What is that
'MFIE' anyway? Management Frame IE? These IEs are not limited to
management frames..
In other words, I would skip all the changes into ieee80211_sta.c and
would only change d80211_mgmt.h to use enum's with old names.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2006-08-07 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-05 8:45 [PATCH wireless-dev] d80211: Switch d80211_mgmt.h to ieee80211.h style definitions Michael Wu
2006-08-07 17:20 ` Jouni Malinen [this message]
2006-08-07 18:37 ` Michael Wu
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=20060807172050.GH4702@instant802.com \
--to=jkm@devicescape.com \
--cc=flamingice@sourmilk.net \
--cc=jbenc@suse.cz \
--cc=linville@tuxdriver.com \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.