From: Randy Dunlap <randy.dunlap@oracle.com>
To: mohamed <mabbas@linux.intel.com>
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com
Subject: Re: [patch 4/5] IEEE 802.11n management action frame data structures
Date: Mon, 26 Mar 2007 16:45:03 -0700 [thread overview]
Message-ID: <20070326164503.f276cd71.randy.dunlap@oracle.com> (raw)
In-Reply-To: <1174909342.1364.60.camel@dell-4965.jf.intel.com>
On Mon, 26 Mar 2007 04:42:22 -0700 mohamed wrote:
> Add draft IEEE 802.11n management action frame data structures and
> constants
>
> Several Action frame format are defined to support IEEE 802.11n
> features.
> This patch add the data structure for Block Ack management action frame.
>
> Signed-off-by: Mohamed Abbas <mabbas@linux.intel.com>
>
> diff -Nupr wireless-dev/include/linux/ieee80211.h
> wireless-dev-new/include/linux/ieee80211.h
> --- wireless-dev/include/linux/ieee80211.h 2007-03-23 13:25:24.000000000
> -0700
> +++ wireless-dev-new/include/linux/ieee80211.h 2007-03-23
> 13:43:21.000000000 -0700
> @@ -105,6 +105,19 @@ struct ieee80211_hdr {
> } __attribute__ ((packed));
>
>
> +struct ieee802_11_addba_param {
> + __le16 reserved:1;
> + __le16 backPolicy:1;
> + __le16 tid:4;
> + __le16 bufSize:10;
> +} __attribute__ ((packed));
> +
> +struct ieee80211_delba_param {
> + __le16 reserved:11;
> + __le16 intiator:1;
> + __le16 tid:4;
> +}__attribute__ ((packed));
These bitfields are all local to one machine, not transported
across a network to systems where the bitfields may be represented
differently?
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2007-03-26 23:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 11:42 [patch 4/5] IEEE 802.11n management action frame data structures mohamed
2007-03-26 23:45 ` Randy Dunlap [this message]
2007-03-28 19:12 ` Johannes Berg
2007-04-04 10:37 ` 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=20070326164503.f276cd71.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mabbas@linux.intel.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).