From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211/cfg80211: report monitor channel in wireless extensions
Date: Tue, 08 Nov 2011 10:56:48 -0800 [thread overview]
Message-ID: <4EB97B70.1010909@candelatech.com> (raw)
In-Reply-To: <1320778327.24797.36.camel@jlt3.sipsolutions.net>
On 11/08/2011 10:52 AM, Johannes Berg wrote:
> From: Johannes Berg<johannes.berg@intel.com>
>
> Just add API to get the channel& report it. Trivial really.
>
> Signed-off-by: Johannes Berg<johannes.berg@intel.com>
> ---
> I'm not sure why this is so hard that the aircrack people
> couldn't figure out what to do ...
>
> include/net/cfg80211.h | 5 +++++
> net/mac80211/cfg.c | 8 ++++++++
> net/wireless/wext-compat.c | 12 ++++++++++++
> 3 files changed, 25 insertions(+)
>
> --- a/include/net/cfg80211.h 2011-11-08 19:37:45.000000000 +0100
> +++ b/include/net/cfg80211.h 2011-11-08 19:49:33.000000000 +0100
> @@ -1342,6 +1342,9 @@ struct cfg80211_gtk_rekey_data {
> * doesn't verify much. Note, however, that the passed netdev may be
> * %NULL as well if the user requested changing the channel for the
> * device itself, or for a monitor interface.
> + * @get_channel: Get the current operating channel, should return %NULL if
> + * there's no signal defined operating channel if for example the
Do you mean "no single defined" ?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2011-11-08 18:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 18:52 [PATCH] mac80211/cfg80211: report monitor channel in wireless extensions Johannes Berg
2011-11-08 18:56 ` Ben Greear [this message]
2011-11-08 19:00 ` Johannes Berg
2011-11-08 19:01 ` [PATCH v2] " Johannes Berg
2011-11-09 9:30 ` [PATCH v3] " Johannes Berg
2011-11-10 9:28 ` Gábor Stefanik
2011-11-10 9:32 ` Johannes Berg
2012-12-22 4:32 ` Richard Farina
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=4EB97B70.1010909@candelatech.com \
--to=greearb@candelatech.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).