From: Larry Finger <Larry.Finger@lwfinger.net>
To: John Linville <linville@tuxdriver.com>, netdev@vger.kernel.org
Subject: Re: [PATCH] Changes to ieee80211.h for user space regulatory daemon
Date: Mon, 05 Jun 2006 16:10:43 -0500 [thread overview]
Message-ID: <44849DD3.9000908@lwfinger.net> (raw)
In-Reply-To: <20060605185905.GH6068@tuxdriver.com>
John W. Linville wrote:
>> @@ -968,6 +968,7 @@ #define IEEE80211_52GHZ_CHANNELS (IEEE80
>>
>> enum {
>> IEEE80211_CH_PASSIVE_ONLY = (1 << 0),
>> + IEEE80211_CH_80211H_RULES = (1 << 1),
>> IEEE80211_CH_B_ONLY = (1 << 2),
>> IEEE80211_CH_NO_IBSS = (1 << 3),
>> IEEE80211_CH_UNIFORM_SPREADING = (1 << 4),
>
> Any idea why this "hole" was here to begin with? Was there something
> else defined as (1 << 1) previously? Is it safe to reuse this value?
>
> John
The hole has been there as long as I have been reading the ieee80211 code. If you are not
comfortable with plugging the hole, then we can use (1 << 5).
Larry
prev parent reply other threads:[~2006-06-05 21:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 16:55 [PATCH] Changes to ieee80211.h for user space regulatory daemon Larry Finger
2006-06-05 18:59 ` John W. Linville
2006-06-05 21:10 ` Larry Finger [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=44849DD3.9000908@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linville@tuxdriver.com \
--cc=netdev@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 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).