From: Michael Wu <flamingice@sourmilk.net>
To: netdev@oss.sgi.com
Cc: ieee80211-devel@lists.sourceforge.net,
James Ketrenos <jketreno@linux.intel.com>
Subject: Re: [PATCH 15/29] ieee80211 Renamed ieee80211_hdr to ieee80211_hdr_4addr
Date: Tue, 13 Sep 2005 19:45:23 -0400 [thread overview]
Message-ID: <200509131945.23126.flamingice@sourmilk.net> (raw)
In-Reply-To: <43275856.7010305@linux.intel.com>
This patch plus patch 5 looks very similar to my management frame patch
except..
On Tuesday 13 September 2005 18:53, James Ketrenos wrote:
> @@ -552,6 +577,17 @@ struct ieee80211_authentication {
> struct ieee80211_info_element info_element[0];
> } __attribute__ ((packed));
>
> +struct ieee80211_disassoc {
Add alias for deauthentication frame here?
> + struct ieee80211_hdr_3addr header;
> + u16 reason_code;
If we do not append _code to "status", why append _code to "reason"?
> + struct ieee80211_info_element info_element[0];
> +} __attribute__ ((packed));
> +
> +struct ieee80211_probe_request {
> + struct ieee80211_hdr_3addr header;
> + struct ieee80211_info_element info_element[0];
> +} __attribute__ ((packed));
> +
> struct ieee80211_probe_response {
> struct ieee80211_hdr_3addr header;
> u32 time_stamp[2];
> @@ -560,14 +596,25 @@ struct ieee80211_probe_response {
> struct ieee80211_info_element info_element[0];
> } __attribute__ ((packed));
>
> -struct ieee80211_assoc_request_frame {
> +/* Alias beacon for probe_response */
> +#define ieee80211_beacon ieee80211_probe_response
> +
> +struct ieee80211_assoc_request {
> + struct ieee80211_hdr_3addr header;
> + u16 capability;
> + u16 listen_interval;
> + struct ieee80211_info_element info_element[0];
> +} __attribute__ ((packed));
> +
> +struct ieee80211_reassoc_request {
> + struct ieee80211_hdr_3addr header;
> __le16 capability;
> __le16 listen_interval;
> u8 current_ap[ETH_ALEN];
> struct ieee80211_info_element info_element[0];
> } __attribute__ ((packed));
>
> -struct ieee80211_assoc_response_frame {
> +struct ieee80211_assoc_response {
> struct ieee80211_hdr_3addr header;
> __le16 capability;
> __le16 status;
parent reply other threads:[~2005-09-13 23:45 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <43275856.7010305@linux.intel.com>]
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=200509131945.23126.flamingice@sourmilk.net \
--to=flamingice@sourmilk.net \
--cc=ieee80211-devel@lists.sourceforge.net \
--cc=jketreno@linux.intel.com \
--cc=netdev@oss.sgi.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