From: "John W. Linville" <linville@tuxdriver.com>
To: Senthil Balasubramanian <senthilkumar@atheros.com>
Cc: linux-wireless@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>,
Jouni Malinen <j@w1.fi>, Luis Rodriguez <lrodriguez@atheros.com>
Subject: Re: [PATCH] wireless: Incorrect LEAP authentication algorithm identifier.
Date: Thu, 4 Dec 2008 10:22:25 -0500 [thread overview]
Message-ID: <20081204152224.GA4989@tuxdriver.com> (raw)
In-Reply-To: <20081204150813.GA7816@senthil-lnx.users.atheros.com>
On Thu, Dec 04, 2008 at 08:38:13PM +0530, Senthil Balasubramanian wrote:
> This patch fixes a regression introduced by
> "wireless: avoid some net/ieee80211.h vs. linux/ieee80211.h conflicts"
> LEAP authentication algorithm identifier should be 128.
>
> Signed-off-by: Senthil Balasubramanian <senthilkumar@atheros.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 a6ec928..c4e6ca1 100644
> --- a/include/linux/ieee80211.h
> +++ b/include/linux/ieee80211.h
> @@ -836,7 +836,7 @@ struct ieee80211_ht_info {
> /* Authentication algorithms */
> #define WLAN_AUTH_OPEN 0
> #define WLAN_AUTH_SHARED_KEY 1
> -#define WLAN_AUTH_LEAP 2
> +#define WLAN_AUTH_LEAP 128
>
> #define WLAN_AUTH_CHALLENGE_LEN 128
What is the regression? What problem does this cause?
AFAICT this value is only used internally, so it shouldn't matter
what the actual value is.
John
--
John W. Linville Linux should be at the core
linville@tuxdriver.com of your literate lifestyle.
next prev parent reply other threads:[~2008-12-04 15:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 15:08 [PATCH] wireless: Incorrect LEAP authentication algorithm identifier Senthil Balasubramanian
2008-12-04 15:22 ` John W. Linville [this message]
2008-12-04 16:20 ` Jouni Malinen
2008-12-04 18:33 ` John W. Linville
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=20081204152224.GA4989@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=senthilkumar@atheros.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).