From: Johannes Berg <johannes@sipsolutions.net>
To: Chet Lanctot <clanctot@codeaurora.org>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/2] nl80211/cfg80211: PMF Requirement communicated to driver with AP SME
Date: Thu, 26 Sep 2013 13:16:00 +0200 [thread overview]
Message-ID: <1380194160.14806.3.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1379446296-22236-3-git-send-email-clanctot@codeaurora.org> (sfid-20130917_213227_344083_0A8DC8D3)
On Tue, 2013-09-17 at 12:31 -0700, Chet Lanctot wrote:
> Needed for drivers that have AP SME integrated. Whether PMF (Protected
> Management Frames, 802.11w) should be used for station connections
> is communicated from upper layer software through nl80211/cfg80211.
This is a bit unclear, what's expected of the driver?
> + if (info->attrs[NL80211_ATTR_USE_MFP]) {
> + params.mfp = nla_get_u32(info->attrs[NL80211_ATTR_USE_MFP]);
> + if (params.mfp != NL80211_MFP_REQUIRED &&
> + params.mfp != NL80211_MFP_OPTIONAL &&
> + params.mfp != NL80211_MFP_NO)
> + return -EINVAL;
> + } else
> + params.mfp = NL80211_MFP_NO;
> +
checkpatch.
johannes
next prev parent reply other threads:[~2013-09-26 11:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 19:31 [PATCH 0/2] nl80211/cfg80211: Support PMF on drivers with integrated AP SME Chet Lanctot
2013-09-17 19:31 ` [PATCH 1/2] nl80211/cfg80211: Driver with AP SME advertises need for PMF SA Query Chet Lanctot
2013-09-26 11:15 ` Johannes Berg
2013-11-27 23:04 ` clanctot
2013-09-17 19:31 ` [PATCH 2/2] nl80211/cfg80211: PMF Requirement communicated to driver with AP SME Chet Lanctot
2013-09-26 11:16 ` Johannes Berg [this message]
2013-11-27 23:16 ` clanctot
2013-09-26 11:09 ` [PATCH 0/2] nl80211/cfg80211: Support PMF on drivers with integrated " Jouni Malinen
2013-10-01 0:43 ` clanctot
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=1380194160.14806.3.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=clanctot@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.