From: Johannes Berg <johannes@sipsolutions.net>
To: Vladimir Koutny <vlado@work.ksp.sk>
Cc: linux-wireless@vger.kernel.org, Daniel Drake <dsd@gentoo.org>
Subject: Re: mac80211: bad use of bss_conf.use_short_preamble
Date: Thu, 27 Mar 2008 14:41:11 +0100 [thread overview]
Message-ID: <1206625271.22530.59.camel@johannes.berg> (raw)
In-Reply-To: <47EB9F93.3060206@work.ksp.sk> (sfid-20080327_132233_178733_0CF971A8)
[-- Attachment #1: Type: text/plain, Size: 339 bytes --]
> does anyone know what values were intended to be used for
> bss_conf.use_short_preamble? The way it is handled now is not
> optimal for sure:
Huh, I guess we screwed that up when converting it to bss_conf. The
WLAN_ERP_... values shouldn't be used internally nor with the driver and
be converted to the bool value.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2008-03-27 13:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 13:22 mac80211: bad use of bss_conf.use_short_preamble Vladimir Koutny
2008-03-27 13:41 ` Johannes Berg [this message]
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=1206625271.22530.59.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=dsd@gentoo.org \
--cc=linux-wireless@vger.kernel.org \
--cc=vlado@work.ksp.sk \
/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