From: Johannes Berg <johannes@sipsolutions.net>
To: Tomas Winkler <tomas.winkler@intel.com>
Cc: linville@tuxdriver.com, yi.zhu@intel.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/2] mac80211: add spectrum capabilities
Date: Wed, 18 Jun 2008 17:37:11 +0200 [thread overview]
Message-ID: <1213803431.1312.24.camel@johannes.berg> (raw)
In-Reply-To: <1213800824-32107-2-git-send-email-tomas.winkler@intel.com>
[-- Attachment #1: Type: text/plain, Size: 989 bytes --]
On Wed, 2008-06-18 at 17:53 +0300, Tomas Winkler wrote:
> This patch add spectrum capability and required information
> elements to association request providing AP has requested it and
> it is supported by the driver
Why bother splitting this up into two patches, the Kconfig option isn't
even being used?
> + if ((bss->capability & WLAN_CAPABILITY_SPECTRUM_MGMT) &&
> + (local->hw.flags & IEEE80211_HW_SPECTRUM_MGMT))
> + capab |= WLAN_CAPABILITY_SPECTRUM_MGMT;
Why do we need a hardware capability flag for this? The only thing you
seem to be doing with it is determine whether to send the power
capability IE?
Will you follow up with more patches to enable radar detection and
things like that, and shouldn't we merge that as one series? This looks
sane enough, but it seems hard to judge whether or not it's actually the
best way to do things.
What else will depend on the hw capability flag?
[and yes, I should read 11h/-2007 again]
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-06-18 15:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 14:53 [PATCH 1/2] mac80211: add MAC80211_VERBOSE_SPECT_MGMT_DEBUG Kconfig option Tomas Winkler
2008-06-18 14:53 ` [PATCH 2/2] mac80211: add spectrum capabilities Tomas Winkler
2008-06-18 15:37 ` Johannes Berg [this message]
2008-06-18 16:17 ` Tomas Winkler
2008-06-18 17:23 ` Johannes Berg
2008-06-18 21:11 ` Tomas Winkler
2008-06-18 21:17 ` Johannes Berg
2008-06-18 21:58 ` Tomas Winkler
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=1213803431.1312.24.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=tomas.winkler@intel.com \
--cc=yi.zhu@intel.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