From: Arend van Spriel <arend@broadcom.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Gautam (Gautam Kumar) Shukla" <gautams@broadcom.com>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Jithu Jance <jithu@broadcom.com>,
Sreenath S <sreenats@broadcom.com>,
Vladimir Kondratiev <vkondrat@qca.qualcomm.com>
Subject: Re: [PATCH 1/1] linux-wireless: Added psk in struct cfg80211_connect_params needed for offloading 4way handshake to driver
Date: Tue, 11 Nov 2014 11:44:42 +0100 [thread overview]
Message-ID: <5461E89A.1060908@broadcom.com> (raw)
In-Reply-To: <1415702338.2163.5.camel@sipsolutions.net>
On 11-11-14 11:38, Johannes Berg wrote:
> On Tue, 2014-11-11 at 11:35 +0100, Arend van Spriel wrote:
>
>> What did pop up is the wiphy flags vs. nl80211 feature flags. When that
>> comes up it looks like 'potAtoes, potaetoes' to me.
>>
>> So is there are clear design rule for when to use which flag. For me the
>> wiphy object represents the device/firmware and 4-way handshake offload
>> support is determined by what the device/firmware supports.
>
> There are three types of flags:
>
> * wiphy flag attributes - deprecated as far as I'm concerned
Ok. deprecated is clear enough ;-)
> * wiphy nl80211 feature flags - much easier to use in kernel (and
> userspace)
> * nl80211 protocol flags - only one exists
> (NL80211_PROTOCOL_FEATURE_SPLIT_WIPHY_DUMP)
Thanks,
Arend
next prev parent reply other threads:[~2014-11-11 10:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 5:56 [PATCH 1/1] linux-wireless: Added psk in struct cfg80211_connect_params needed for offloading 4way handshake to driver Gautam (Gautam Kumar) Shukla
[not found] ` <DF163EE1A432BF4BBE6B2088220663A67437BD-HXj2mutaA2pmqaqore1TH5r/X4hKkxxPpWgKQ6/u3Fg@public.gmane.org>
2014-11-11 9:29 ` Johannes Berg
2014-11-11 9:54 ` Arend van Spriel
2014-11-11 10:03 ` Johannes Berg
[not found] ` <1415700220.2163.3.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2014-11-11 10:35 ` Arend van Spriel
2014-11-11 10:38 ` Johannes Berg
2014-11-11 10:44 ` Arend van Spriel [this message]
[not found] ` <5461DCC9.5050702-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2014-11-11 10:33 ` Gautam (Gautam Kumar) Shukla
2014-11-11 9:44 ` 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=5461E89A.1060908@broadcom.com \
--to=arend@broadcom.com \
--cc=davem@davemloft.net \
--cc=gautams@broadcom.com \
--cc=jithu@broadcom.com \
--cc=johannes@sipsolutions.net \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=sreenats@broadcom.com \
--cc=vkondrat@qca.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).