From: Johannes Berg <johannes@sipsolutions.net>
To: Alexander Simon <an.alexsimon@googlemail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 1/4] nl80211: Parse channel type attribute in an IBSS join request
Date: Wed, 31 Aug 2011 08:36:17 +0200 [thread overview]
Message-ID: <1314772577.4161.12.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <2053881.ENil2Dy3QM@alex-1> (sfid-20110829_161556_944174_8A64BBCC)
On Mon, 2011-08-29 at 16:15 +0200, Alexander Simon wrote:
> +/**
> + * cfg80211_can_use_ext_chan - test if ht40 on extension channel can be used
> + * @wiphy: the wiphy
> + * @chan: main channel
> + * @channel_type: HT mode
> + */
> +bool cfg80211_can_use_ext_chan(struct wiphy *wiphy,
> + struct ieee80211_channel *chan,
> + enum nl80211_channel_type channel_type);
Use for what? That's confusing. You're asking if it can be used for
beaconing, as the old function name *clearly* said. Now you're making it
confusing.
johannes
next prev parent reply other threads:[~2011-08-31 6:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 14:15 [PATCH v2 1/4] nl80211: Parse channel type attribute in an IBSS join request Alexander Simon
2011-08-29 14:30 ` [PATCH v2 2/4] cfg80211: Add cfg80211_get_bss_ht to also match HT configuration Alexander Simon
2011-08-31 6:37 ` Johannes Berg
2011-09-09 14:07 ` Marek Lindner
2011-08-29 14:31 ` [PATCH v2 3/4] mac80211: Add HT helper functions Alexander Simon
2011-08-31 6:38 ` Johannes Berg
2011-08-29 14:32 ` [PATCH v2 4/4] mac80211: Add HT operation modes for IBSS Alexander Simon
2011-09-09 14:17 ` Marek Lindner
2011-08-31 6:36 ` Johannes Berg [this message]
2011-08-31 13:49 ` [PATCH v2 1/4] nl80211: Parse channel type attribute in an IBSS join request Alexander Simon
2011-09-01 13:18 ` Johannes Berg
2011-08-31 15:51 ` Marek Lindner
2011-08-31 16:44 ` Alexander Simon
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=1314772577.4161.12.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=an.alexsimon@googlemail.com \
--cc=linux-wireless@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 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.