From: Johannes Berg <johannes@sipsolutions.net>
To: "Kushwaha, Purushottam" <pkushwah@qti.qualcomm.com>,
"Undekari, Sunil Dutt" <usdutt@qti.qualcomm.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Malinen, Jouni" <jouni@qca.qualcomm.com>,
"Hullur Subramanyam, Amarnath" <amarnath@qca.qualcomm.com>
Subject: Re: [PATCH v8] cfg80211: Provision to allow the support for different beacon intervals
Date: Fri, 07 Oct 2016 09:47:13 +0200 [thread overview]
Message-ID: <1475826433.2015.25.camel@sipsolutions.net> (raw)
In-Reply-To: <6c2abcf3f79b4cf6996b69e1a7aa590d@aphydexm01b.ap.qualcomm.com>
On Fri, 2016-10-07 at 07:42 +0000, Kushwaha, Purushottam wrote:
> >
> > However, it seems pretty easy to solve by passing another bool that
> > indicates "all the same"?
> Yes . Thanks .
> We are planning to get the following changes in 2 commits . Let me
> know your consent .
> 1. cfg80211: Provision to allow the support for different beacon
> intervals. ( Would like to go with this in a separate commit as the
> current infrastructure also does not support the validation of
> radar_detect / num_different_channel ) .
> 2. cfg80211 : Check radar_detect and num_different_channels with
> beacon interface combinations.
>
Seems fine, no driver will be able to advertise the different BIs
inbetween the two patches anyway.
I think we might want to add another patch before or inbetween, that
converts the far-too-long argument list of the combination
iter/validation functions to a structure?
johannes
prev parent reply other threads:[~2016-10-07 7:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 13:26 [PATCH v8] cfg80211: Provision to allow the support for different beacon intervals Purushottam Kushwaha
2016-09-12 10:24 ` Johannes Berg
2016-09-16 6:34 ` Undekari, Sunil Dutt
2016-09-27 13:02 ` Johannes Berg
2016-09-27 15:36 ` Undekari, Sunil Dutt
2016-09-28 11:21 ` Johannes Berg
2016-10-07 7:42 ` Kushwaha, Purushottam
2016-10-07 7:47 ` 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=1475826433.2015.25.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=amarnath@qca.qualcomm.com \
--cc=jouni@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pkushwah@qti.qualcomm.com \
--cc=usdutt@qti.qualcomm.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.