From: Kalle Valo <kvalo@codeaurora.org>
To: Avinash Patil <patila@marvell.com>
Cc: <linux-wireless@vger.kernel.org>, <akarwar@marvell.com>,
<cluo@marvell.com>, <gaoqs@marvell.com>,
Avinash Patil <patila@marvell.com>
Subject: Re: [v2, 01/10] mwifiex: do not send regulatory update while starting AP
Date: Thu, 29 Jan 2015 08:26:04 +0000 (UTC) [thread overview]
Message-ID: <20150129082604.39A6413FF33@smtp.codeaurora.org> (raw)
In-Reply-To: <1422440665-3940-2-git-send-email-patila@marvell.com>
> When regulatory domain changes, cfg80211 already issues request
> to change regulatory domain to driver via reg_notifier.
> There is no need to set regulatory again during start_ap.
>
> Signed-off-by: Avinash Patil <patila@marvell.com>
> Signed-off-by: Qingshui Gao <gaoqs@marvell.com>
> Signed-off-by: Cathy Luo <cluo@marvell.com>
Thanks, 10 patches applied to wireless-drivers-next.git:
6144369f8b4b mwifiex: do not send regulatory update while starting AP
35c739b50d78 mwifiex: store AP configuration in private structure
b0d4c5ec9730 mwifiex: update IEs after AP has started
b654ca182a2f mwifiex: refactor start_ap handler
2ade5667e2e0 mwifiex: separate function for parsing head and tail IEs
85afb18621be mwifiex: add cfg80211 start_radar_detection handler
0a694d68651b mwifiex: support for channel report for radar detection
3b57c1a713a9 mwifiex: handle radar detect event from FW
7d652034d1a0 mwifiex: channel switch support for mwifiex
cf075eac9ca9 mwifiex: 11h handling for AP interface
Kalle Valo
next prev parent reply other threads:[~2015-01-29 8:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 10:24 [PATCH v2 00/10] mwifiex: DFS support for mwifiex AP Avinash Patil
2015-01-28 10:24 ` [PATCH v2 01/10] mwifiex: do not send regulatory update while starting AP Avinash Patil
2015-01-29 8:26 ` Kalle Valo [this message]
2015-01-28 10:24 ` [PATCH v2 02/10] mwifiex: store AP configuration in private structure Avinash Patil
2015-01-28 10:24 ` [PATCH v2 03/10] mwifiex: update IEs after AP has started Avinash Patil
2015-01-28 10:24 ` [PATCH v2 04/10] mwifiex: refactor start_ap handler Avinash Patil
2015-01-28 10:24 ` [PATCH v2 05/10] mwifiex: separate function for parsing head and tail IEs Avinash Patil
2015-01-28 10:24 ` [PATCH v2 06/10] mwifiex: add cfg80211 start_radar_detection handler Avinash Patil
2015-01-28 10:24 ` [PATCH v2 07/10] mwifiex: support for channel report for radar detection Avinash Patil
2015-01-28 10:24 ` [PATCH v2 08/10] mwifiex: handle radar detect event from FW Avinash Patil
2015-01-28 10:24 ` [PATCH v2 09/10] mwifiex: channel switch support for mwifiex Avinash Patil
2015-01-28 10:24 ` [PATCH v2 10/10] mwifiex: 11h handling for AP interface Avinash Patil
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=20150129082604.39A6413FF33@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=akarwar@marvell.com \
--cc=cluo@marvell.com \
--cc=gaoqs@marvell.com \
--cc=linux-wireless@vger.kernel.org \
--cc=patila@marvell.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 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.