linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: Johannes Berg <johannes@sipsolutions.net>,
	"John W. Linville" <linville@tuxdriver.com>
Cc: <linux-wireless@vger.kernel.org>, Arend van Spriel <arend@broadcom.com>
Subject: [RFC 0/3] brcmfmac: provide band info upon wiphy registration
Date: Tue, 17 Jun 2014 11:16:18 +0200	[thread overview]
Message-ID: <1402996581-10764-1-git-send-email-arend@broadcom.com> (raw)

This short series rely on a cfg80211 API so making this a RFC. It
applies to master branch of the wireless-next repository.

Arend van Spriel (3):
  brcmfmac: move attach and detach functions in wl_cfg80211.c
  cfg80211: expose cfg80211_disable_40mhz_24ghz module parameter
  brcmfmac: update band and regulatory info before wiphy_register()

 .../net/wireless/brcm80211/brcmfmac/wl_cfg80211.c  | 240 ++++++++++-----------
 include/net/cfg80211.h                             |   9 +
 net/wireless/core.c                                |   6 +
 3 files changed, 130 insertions(+), 125 deletions(-)

-- 
1.9.1


             reply	other threads:[~2014-06-17  9:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-17  9:16 Arend van Spriel [this message]
2014-06-17  9:16 ` [RFC 1/3] brcmfmac: move attach and detach functions in wl_cfg80211.c Arend van Spriel
2014-06-17  9:16 ` [RFC 2/3] cfg80211: expose cfg80211_disable_40mhz_24ghz module parameter Arend van Spriel
2014-06-23  9:34   ` Johannes Berg
2014-06-24 17:21     ` Arend van Spriel
2014-06-25 15:57       ` Johannes Berg
2014-06-25 16:50         ` Arend van Spriel
2014-06-17  9:16 ` [RFC 3/3] brcmfmac: update band and regulatory info before wiphy_register() Arend van Spriel
2014-06-23  9:37   ` Johannes Berg
2014-06-24 17:11     ` Arend van Spriel
2014-06-25 15:55       ` Johannes Berg

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=1402996581-10764-1-git-send-email-arend@broadcom.com \
    --to=arend@broadcom.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).