From: Johannes Berg <johannes@sipsolutions.net>
To: Peng Xu <pxu@qti.qualcomm.com>, Jouni Malinen <jouni@qca.qualcomm.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Sara Sharon <sara.sharon@intel.com>
Subject: Re: [RFC] cfg80211: Implement Multiple BSSID capability in scanning
Date: Tue, 14 Nov 2017 15:33:15 +0100 [thread overview]
Message-ID: <1510669995.2030.26.camel@sipsolutions.net> (raw)
In-Reply-To: <929d1fdb74524aeaab4959f84a82c732@NASANEXM01F.na.qualcomm.com>
> >
> > This may be right for the WFA/Microsoft OUI, but not necessary anything
> > else?
> >
>
> Right, I only considered the most common cases since I did not find a
> generic way to compare two vendor elements. Any suggestion?
Right, not really.
I'm not even sure why this is necessary anyway though, do we really
think vendors will expect to be able to put vendor IEs inside the
subelements and override the ones outside?
Is there even any point for the WFA ones? It seems WMM really ought to
be the same for all anyway, for example.
johannes
next prev parent reply other threads:[~2017-11-14 14:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 16:39 [RFC] cfg80211: Implement Multiple BSSID capability in scanning Jouni Malinen
2017-11-13 10:07 ` Johannes Berg
2017-11-14 12:58 ` Johannes Berg
2017-11-14 14:20 ` Peng Xu
2017-11-14 14:23 ` Johannes Berg
2017-11-14 14:29 ` Peng Xu
2017-11-14 14:33 ` Johannes Berg [this message]
2017-11-14 14:39 ` Peng Xu
2017-11-14 16:31 ` Jouni Malinen
2017-11-14 17:38 ` Peng Xu
2017-11-27 12:03 ` Johannes Berg
2017-11-27 19:14 ` Peng Xu
2017-11-27 21:46 ` 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=1510669995.2030.26.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=jouni@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pxu@qti.qualcomm.com \
--cc=sara.sharon@intel.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).