linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Pontus Fuchs <pontus.fuchs@gmail.com>
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 09:34:45 +0200	[thread overview]
Message-ID: <1333524885.3912.2.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1333463998-19329-1-git-send-email-pontus.fuchs@gmail.com> (sfid-20120403_164012_468794_1452235E)

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.
> 
> Signed-off-by: Pontus Fuchs <pontus.fuchs@gmail.com>
> ---
>  include/net/cfg80211.h     |    3 ++-
>  net/mac80211/cfg.c         |    4 +++-
>  net/wireless/nl80211.c     |   13 +++++++++++++
>  net/wireless/wext-compat.c |    3 ++-
>  4 files changed, 20 insertions(+), 3 deletions(-)
> 
> diff --git a/include/net/cfg80211.h b/include/net/cfg80211.h
> index 83d800c..a1b202c 100644
> --- a/include/net/cfg80211.h
> +++ b/include/net/cfg80211.h
> @@ -1698,7 +1698,8 @@ struct cfg80211_ops {
>  				  struct net_device *dev,
>  				  u16 noack_map);
>  
> -	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?

johannes


  reply	other threads:[~2012-04-04  7:34 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 [this message]
2012-04-04  8:45   ` Pontus Fuchs

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=1333524885.3912.2.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=pontus.fuchs@gmail.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).