From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John Linville <linville@tuxdriver.com>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] cfg80211: fix static regdomains
Date: Mon, 15 Sep 2008 10:01:37 -0700 [thread overview]
Message-ID: <20080915170137.GD22572@tesla> (raw)
In-Reply-To: <1221467435.3700.27.camel@johannes.berg>
On Mon, Sep 15, 2008 at 01:30:34AM -0700, Johannes Berg wrote:
> When Luis added the static regdomains back he used +/-20
> of the centre frequencies to account for 40MHz bandwidth
> neglecting the fact that 40MHz bandwidth cannot be used
> on the channels close to the allowed band edges.
Good catch, not sure exactly where this applies but since
the static stuff will die soon sure, its better to be safe.
Luis
prev parent reply other threads:[~2008-09-15 17:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-15 8:30 [PATCH] cfg80211: fix static regdomains Johannes Berg
2008-09-15 17:01 ` Luis R. Rodriguez [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=20080915170137.GD22572@tesla \
--to=lrodriguez@atheros.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.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).