From: Felix Fietkau <nbd@openwrt.org>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: fix ieee80211_meshconf_ie::meshconf_cap type to be u16
Date: Sun, 04 Apr 2010 11:07:11 -0700 [thread overview]
Message-ID: <4BB8D54F.7060906@openwrt.org> (raw)
In-Reply-To: <1270375964-23668-1-git-send-email-jcmvbkbc@gmail.com>
On 2010-04-04 3:12 AM, Max Filippov wrote:
> According to the current 802.11s draft mesh capability field
> is 16 bits wide.
>
> Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
> ---
> include/linux/ieee80211.h | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/include/linux/ieee80211.h b/include/linux/ieee80211.h
> index 1998495..910b4bc 100644
> --- a/include/linux/ieee80211.h
> +++ b/include/linux/ieee80211.h
> @@ -604,7 +604,7 @@ struct ieee80211_meshconf_ie {
> u8 meshconf_synch;
> u8 meshconf_auth;
> u8 meshconf_form;
> - u8 meshconf_cap;
> + u16 meshconf_cap;
Shouldn't that be __le16? You probably also have to add le16_to_cpu in
the place that accesses this field, otherwise this introduces an endian bug.
- Felix
next prev parent reply other threads:[~2010-04-04 18:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-04 10:12 [PATCH] mac80211: fix ieee80211_meshconf_ie::meshconf_cap type to be u16 Max Filippov
2010-04-04 18:07 ` Felix Fietkau [this message]
2010-04-04 19:39 ` Max Filippov
2010-04-04 19:50 ` [PATCH] mac80211: fix ieee80211_meshconf_ie::meshconf_cap type to be __le16 Max Filippov
2010-04-04 19:45 ` [PATCH] mac80211: fix ieee80211_meshconf_ie::meshconf_cap type to be u16 Ледовских Николай Валерьевич
2010-04-04 19:59 ` Max Filippov
2010-04-05 7:38 ` Jouni Malinen
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=4BB8D54F.7060906@openwrt.org \
--to=nbd@openwrt.org \
--cc=jcmvbkbc@gmail.com \
--cc=linux-wireless@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.