From: Johannes Berg <johannes@sipsolutions.net>
To: Dmitry Shmidt <dimitrysh@google.com>
Cc: Arend Van Spriel <arend.vanspriel@broadcom.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] RFC: Universal scan proposal
Date: Wed, 04 Jan 2017 14:28:30 +0100 [thread overview]
Message-ID: <1483536510.7312.5.camel@sipsolutions.net> (raw)
In-Reply-To: <CAH7ZN-zm-CUv=QzoUojdyrcONRAHtTG18PiwGZ4sYY0qqft1BA@mail.gmail.com> (sfid-20170103_214601_693369_864810F8)
On Tue, 2017-01-03 at 12:45 -0800, Dmitry Shmidt wrote:
>
> We can either use alternative structure in kernel wireless stack,
> or alternative structure in userspace (in wpa_supplicant), and we
> will most likely need special command for this case at least to
> retrieve results.
Yes, I tend to agree - we need to have some new structure (and netlink
attributes etc.) to report the aggregated/partial results. But it seems
to me that it'll have to be very obvious which way of obtaining results
must be used for a given scan?
johannes
next prev parent reply other threads:[~2017-01-04 13:28 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 22:47 [PATCH] RFC: Universal scan proposal dimitrysh
2016-11-17 20:56 ` Arend Van Spriel
2016-11-18 23:53 ` Dmitry Shmidt
2016-11-22 7:24 ` Luca Coelho
2016-11-22 17:29 ` Dmitry Shmidt
2016-11-22 20:41 ` Arend Van Spriel
2016-11-22 20:54 ` Dmitry Shmidt
2016-11-23 8:43 ` Arend Van Spriel
2016-11-28 19:25 ` Dmitry Shmidt
2016-12-05 14:28 ` Johannes Berg
2016-12-05 18:32 ` Dmitry Shmidt
2016-12-07 6:44 ` Johannes Berg
2016-12-07 18:39 ` Dmitry Shmidt
2016-12-07 20:51 ` Arend Van Spriel
2016-12-08 22:35 ` Dmitry Shmidt
2016-12-09 11:10 ` Arend Van Spriel
2016-12-13 16:06 ` Johannes Berg
2017-01-03 20:45 ` Dmitry Shmidt
2017-01-04 13:28 ` Johannes Berg [this message]
2017-01-04 20:32 ` Dmitry Shmidt
2017-01-05 11:46 ` Johannes Berg
2017-01-05 13:39 ` Arend Van Spriel
2017-01-05 13:44 ` Johannes Berg
2017-01-05 19:59 ` Arend Van Spriel
2017-01-09 10:48 ` Johannes Berg
2017-01-09 12:07 ` Arend Van Spriel
2017-01-11 13:14 ` Johannes Berg
2017-01-05 20:45 ` Dmitry Shmidt
2017-01-09 10:45 ` Johannes Berg
2017-01-09 11:19 ` Arend Van Spriel
2016-12-13 16:04 ` Johannes Berg
2016-12-21 10:20 ` [RFC] nl80211: allow multiple active scheduled scan requests Arend van Spriel
2017-01-02 10:44 ` Johannes Berg
2017-01-03 12:25 ` Arend Van Spriel
2017-01-04 9:59 ` Johannes Berg
2017-01-04 10:20 ` Arend Van Spriel
2017-01-04 10:30 ` Johannes Berg
2017-01-04 10:34 ` Arend Van Spriel
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=1483536510.7312.5.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@broadcom.com \
--cc=dimitrysh@google.com \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).