From: Johannes Berg <johannes@sipsolutions.net>
To: Seth Forshee <seth.forshee@canonical.com>
Cc: linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
"Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>,
Josh Boyer <jwboyer@redhat.com>,
Arend van Spriel <arend@broadcom.com>,
Brett Rudley <brudley@broadcom.com>,
Roland Vossen <rvossen@broadcom.com>,
brcm80211-dev-list@broadcom.com
Subject: Re: [PATCH 1/2] cfg80211: add channel flag to prohibit OFDM operation
Date: Thu, 02 Aug 2012 15:31:20 +0200 [thread overview]
Message-ID: <1343914280.4471.0.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20120802130431.GA32395@thinkpad-t410>
On Thu, 2012-08-02 at 08:04 -0500, Seth Forshee wrote:
> On Thu, Aug 02, 2012 at 08:24:20AM +0200, Johannes Berg wrote:
> > On Wed, 2012-08-01 at 15:58 -0500, Seth Forshee wrote:
> > > Currently the only way for wireless drivers to tell whether or not OFDM
> > > is allowed on the current channel is to check the regulatory
> > > information. However, this requires hodling cfg80211_mutex, which is not
> > > visible to the drivers.
> > >
> > > Other regulatory restrictions are provided as flags in the channel
> > > definition, so let's do similarly with OFDM. This patch adds a new flag,
> > > IEEE80211_CHAN_NO_OFDM, to tell drivers that OFDM on a channel is not
> > > allowed. This flag is set on any channels for which regulatory indicates
> > > that OFDM is prohibited.
> >
> > Looks good, this needs to go into 3.6, right?
>
> Yes, it should go into 3.6.
Alright, applied.
johannes
next prev parent reply other threads:[~2012-08-02 13:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 20:58 [PATCH 0/2] Fix lockdep warning in brcmsmac Seth Forshee
2012-08-01 20:58 ` [PATCH 1/2] cfg80211: add channel flag to prohibit OFDM operation Seth Forshee
2012-08-01 21:20 ` Luis R. Rodriguez
2012-08-02 6:24 ` Johannes Berg
2012-08-02 13:04 ` Seth Forshee
2012-08-02 13:31 ` Johannes Berg [this message]
2012-08-01 20:58 ` [PATCH 2/2] brcmsmac: use channel flags to restrict OFDM Seth Forshee
2012-08-02 0:23 ` [PATCH 0/2] Fix lockdep warning in brcmsmac Josh Boyer
2012-08-02 1:53 ` Seth Forshee
2012-08-02 12:02 ` Josh Boyer
2012-08-02 12:51 ` Josh Boyer
2012-08-02 13:42 ` Arend van Spriel
2012-08-02 13:45 ` Josh Boyer
2012-08-02 14:00 ` Arend van Spriel
2012-08-02 14:45 ` Josh Boyer
2012-08-02 14:49 ` Josh Boyer
2012-08-02 13:44 ` Hauke Mehrtens
2012-08-02 13:54 ` Josh Boyer
2012-08-02 11:01 ` Arend van Spriel
2012-08-02 11:39 ` Arend van Spriel
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=1343914280.4471.0.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=brudley@broadcom.com \
--cc=jwboyer@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rodrigue@qca.qualcomm.com \
--cc=rvossen@broadcom.com \
--cc=seth.forshee@canonical.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 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.