linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avinash Patil <patila@marvell.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Amitkumar Karwar <akarwar@marvell.com>,
	Cathy Luo <cluo@marvell.com>, "Marc Yang" <yangyang@marvell.com>,
	Qingshui Gao <gaoqs@marvell.com>
Subject: Re: [PATCH 00/10] mwifiex: DFS support for mwifiex AP
Date: Tue, 27 Jan 2015 16:44:50 +0530	[thread overview]
Message-ID: <1422357290.20608.0.camel@pe-lt950> (raw)
In-Reply-To: <87d265l3u2.fsf@kamboji.qca.qualcomm.com>

On Fri, 2015-01-23 at 11:00 -0800, Kalle Valo wrote:
> Avinash Patil <patila@marvell.com> writes:
> 
> > This patch series adds DFS support for mwifiex AP. Series include
> > patches to handle cfg80211 start_radar_detection and channel_switch
> > handlers. First 5 patches are actually refactoring effort. Patch6-10
> > add these handlers and other DFS handling.
> >
> > Avinash Patil (10):
> >   mwifiex: do not send regulatory update while starting AP
> >   mwifiex: store AP configuration in private structure
> >   mwifiex: update IEs after AP has started
> >   mwifiex: refactor start_ap handler
> >   mwifiex: separate function for parsing head and tail IEs
> >   mwifiex: add cfg80211 start_radar_detection handler
> >   mwifiex: support for channel report for radar detection
> >   mwifiex: handle radar detect event from FW
> >   mwifiex: channel switch support for mwifiex
> >   mwifiex: 11h handling for AP interface
> 
> Patch 5 had conflicts, please rebase.
> 
Hi Kalle,

I will rebase patches on top of master and resend.

Thanks,
Avinash



      reply	other threads:[~2015-01-27  5:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-14 16:15 [PATCH 00/10] mwifiex: DFS support for mwifiex AP Avinash Patil
2015-01-14 16:15 ` [PATCH 01/10] mwifiex: do not send regulatory update while starting AP Avinash Patil
2015-01-14 16:15 ` [PATCH 02/10] mwifiex: store AP configuration in private structure Avinash Patil
2015-01-14 16:15 ` [PATCH 03/10] mwifiex: update IEs after AP has started Avinash Patil
2015-01-14 16:15 ` [PATCH 04/10] mwifiex: refactor start_ap handler Avinash Patil
2015-01-14 16:15 ` [PATCH 05/10] mwifiex: separate function for parsing head and tail IEs Avinash Patil
2015-01-14 16:15 ` [PATCH 06/10] mwifiex: add cfg80211 start_radar_detection handler Avinash Patil
2015-01-14 16:15 ` [PATCH 07/10] mwifiex: support for channel report for radar detection Avinash Patil
2015-01-14 16:15 ` [PATCH 08/10] mwifiex: handle radar detect event from FW Avinash Patil
2015-01-14 16:15 ` [PATCH 09/10] mwifiex: channel switch support for mwifiex Avinash Patil
2015-01-14 16:15 ` [PATCH 10/10] mwifiex: 11h handling for AP interface Avinash Patil
2015-01-23 19:00 ` [PATCH 00/10] mwifiex: DFS support for mwifiex AP Kalle Valo
2015-01-27 11:14   ` Avinash Patil [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=1422357290.20608.0.camel@pe-lt950 \
    --to=patila@marvell.com \
    --cc=akarwar@marvell.com \
    --cc=cluo@marvell.com \
    --cc=gaoqs@marvell.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=yangyang@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 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).