From: Johannes Berg <johannes@sipsolutions.net>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>,
"Malinen, Jouni" <jouni@qca.qualcomm.com>
Cc: "Vamsi, Krishna" <vamsin@qti.qualcomm.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] cfg80211: Add support to sched scan to report better BSSs
Date: Wed, 04 Jan 2017 14:32:14 +0100 [thread overview]
Message-ID: <1483536734.7312.7.camel@sipsolutions.net> (raw)
In-Reply-To: <c807ce00-46bb-e214-8bef-3544e301aad6@broadcom.com> (sfid-20161221_101814_323016_46561D57)
> Also I don't see the array issue. @relative_rssi_5g_pref with s8
> value seems same as @rssi_adjust with (band=5g, s8 value) packed
> together. Or am I missing something here.
Jouni is arguing that if you can specify which band to adjust, you
might want to adjust more than one band - and need an array of
(band,adjustment) rather than just a single such tuple.
But if we introduce this attribute with the tuple now, we can extend it
to an array of tuples later if we really need that.
johannes
next prev parent reply other threads:[~2017-01-04 13:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 21:59 [PATCH v2 1/2] nl80211: Use different attrs for BSSID and random MAC addr in scan req Jouni Malinen
2016-12-02 21:59 ` [PATCH v2 2/2] cfg80211: Add support to sched scan to report better BSSs Jouni Malinen
2016-12-07 9:25 ` Johannes Berg
2016-12-07 9:33 ` Vamsi, Krishna
2016-12-07 20:03 ` Arend Van Spriel
2016-12-08 17:52 ` Malinen, Jouni
2016-12-08 20:35 ` Arend Van Spriel
2016-12-13 15:56 ` Johannes Berg
2016-12-15 11:06 ` Malinen, Jouni
2016-12-16 9:56 ` Johannes Berg
2016-12-20 20:52 ` Malinen, Jouni
2016-12-21 9:18 ` Arend Van Spriel
2017-01-04 13:32 ` Johannes Berg [this message]
2017-01-04 13:34 ` Johannes Berg
2016-12-07 20:11 ` 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=1483536734.7312.7.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@broadcom.com \
--cc=jouni@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=vamsin@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 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).