From: Pontus Fuchs <pontus.fuchs@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] cfg80211: Add channel information to NL80211_CMD_GET_INTERFACE
Date: Wed, 04 Apr 2012 10:45:05 +0200 [thread overview]
Message-ID: <4F7C0A11.5090808@gmail.com> (raw)
In-Reply-To: <1333524885.3912.2.camel@jlt3.sipsolutions.net>
On 2012-04-04 09:34, Johannes Berg wrote:
> On Tue, 2012-04-03 at 16:39 +0200, Pontus Fuchs wrote:
>> If the current channel is known, add frequency and channel type to
>> NL80211_CMD_GET_INTERFACE.
>>
...
>> - struct ieee80211_channel *(*get_channel)(struct wiphy *wiphy);
>> + struct ieee80211_channel *(*get_channel)(struct wiphy *wiphy,
>> + enum nl80211_channel_type *type);
>
> If you're adding it to GET_INTERFACE, maybe you should also get it per
> interface so we can do something smarter when we add multi-channel?
We'll fix multi-channel later if needed. Main usage for this (from my
point of view) is for monitor interfaces.
Cheers,
Pontus
prev parent reply other threads:[~2012-04-04 8:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 14:39 [PATCH] cfg80211: Add channel information to NL80211_CMD_GET_INTERFACE Pontus Fuchs
2012-04-04 7:34 ` Johannes Berg
2012-04-04 8:45 ` Pontus Fuchs [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=4F7C0A11.5090808@gmail.com \
--to=pontus.fuchs@gmail.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).