linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Avinash Patil <avinashapatil@gmail.com>
Cc: linux-wireless@vger.kernel.org, John Linville <linville@tuxdriver.com>
Subject: Re: [RFC 2/2] cfg80211: provide channel to start_ap function
Date: Fri, 11 May 2012 12:12:33 +0200	[thread overview]
Message-ID: <1336731153.4310.20.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <CAJwzM1=hFmaj-tA7ru2Li9c2EGL5wbPbcGoA6aws=f+dRNmvTA@mail.gmail.com> (sfid-20120511_120401_713989_11A9A313)

On Fri, 2012-05-11 at 15:33 +0530, Avinash Patil wrote:
> How does mwifiex work with this? Is it easier/harder to do?
> 
> set_channel handler from cfg80211 is issued first where we set channel
> to FW. After that in start_ap, we set beacon, dtim interval, SSID,
> security etc and start AP.
> Its easier to move to new implementation, but unit testing and
> internal review of this patch may take some time and by then merge
> window may expire.

I'll have to let you sort this out with John. I don't know if he is
planning to merge either of our patches for 3.5.

If he picks up your code before mine though, be prepared that I'll just
resend my code fixing up mwifiex in the most simple way and will not
really be worried about your unit testing/internal review. If you want
to help me out though you could make a small patch that adjusts your
code to the new API and send it to me/the list separately from your
submission.

johannes


      reply	other threads:[~2012-05-11 10:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-10 20:30 [RFC 0/2] simplify AP channel setting Johannes Berg
2012-05-10 20:30 ` [RFC 1/2] mac80211: move ieee80211_set_channel function Johannes Berg
2012-05-11  6:36   ` Michal Kazior
2012-05-11  6:39     ` Johannes Berg
2012-05-10 20:30 ` [RFC 2/2] cfg80211: provide channel to start_ap function Johannes Berg
2012-05-11  9:51   ` Avinash Patil
2012-05-11  9:55     ` Johannes Berg
2012-05-11  9:56       ` Johannes Berg
2012-05-11 10:03       ` Avinash Patil
2012-05-11 10:12         ` Johannes Berg [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=1336731153.4310.20.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=avinashapatil@gmail.com \
    --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).