From: Johannes Berg <johannes@sipsolutions.net>
To: Sathishkumar Muruganandam <murugana@codeaurora.org>
Cc: linux-wireless@vger.kernel.org, ath11k@lists.infradead.org
Subject: Re: [EXT] Re: [PATCH v2 0/2] add Wide Band Scan support
Date: Tue, 05 Nov 2019 11:22:52 +0100 [thread overview]
Message-ID: <867302d58d3183ce7e2c7afa846027a787579b87.camel@sipsolutions.net> (raw)
In-Reply-To: <00d301d593c2$bd37d8f0$37a78ad0$@codeaurora.org>
On Tue, 2019-11-05 at 15:51 +0530, Sathishkumar Muruganandam wrote:
> > Neither of these are scan use cases (at least not that are covered by
> > nl80211 scan APIs), so that doesn't make sense.
> >
>
> Actually we had extended the existing 'iw scan' command to do Wide
> Band Scan using nl80211 scan APIs.
Yes ... but ... that doesn't address my question.
How is this related to scanning? It sounds to me like you're just
(ab)using scan as a somewhat convenient "do some channel hopping" API
...
johannes
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2019-11-05 10:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 12:09 [PATCH v2 0/2] add Wide Band Scan support Sathishkumar Muruganandam
2019-11-04 12:09 ` [PATCH v2 1/2] nl80211: " Sathishkumar Muruganandam
2019-11-04 12:09 ` [PATCH v2 2/2] ath11k: " Sathishkumar Muruganandam
2019-11-04 12:11 ` [PATCH v2 0/2] " Johannes Berg
2019-11-05 10:21 ` [EXT] " Sathishkumar Muruganandam
2019-11-05 10:22 ` Johannes Berg [this message]
2019-11-11 7:57 ` Sathishkumar Muruganandam
2019-11-14 6:38 ` Johannes Berg
2019-11-14 12:33 ` Sathishkumar Muruganandam
2019-11-22 12:45 ` 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=867302d58d3183ce7e2c7afa846027a787579b87.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=murugana@codeaurora.org \
/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