From: Johannes Berg <johannes@sipsolutions.net>
To: clanctot@codeaurora.org
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/2 V3] nl80211/cfg80211: Enable station PMF requirement to be specified to driver with AP SME
Date: Mon, 06 Jan 2014 17:40:03 +0100 [thread overview]
Message-ID: <1389026403.5891.36.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <508ee22698c0bc2a2387a23158c97e8d.squirrel@www.codeaurora.org>
On Fri, 2014-01-03 at 21:30 +0000, clanctot@codeaurora.org wrote:
> >> + } else
> >> + params.mfp = NL80211_MFP_NO;
> > Code style.
> For the issue of code style, I am not sure what you mean here. I copied
> this code from the nl80211_connect routine, which has similar processing
> for a “use MFP” parameter. I tried to make the code I added be consistent
> with this existing code.
>
> If you explain what needs to be changed to improve the code style, I will
> make the changes.
All branches should (now) have braces if one of them requires it.
> Regarding your question about a feature flag, there is already a flag
> that indicates that the driver implements the AP SME:
> * @WIPHY_FLAG_HAVE_AP_SME: device integrates AP SME
> Is this the type of flag you were referring to?
Yes, but it seems to me that you need a flag in the nl80211 API
indicating that the AP SME supports PMF in this way.
johannes
next prev parent reply other threads:[~2014-01-06 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 21:30 [PATCH 2/2 V3] nl80211/cfg80211: Enable station PMF requirement to be specified to driver with AP SME clanctot
2014-01-06 16:40 ` Johannes Berg [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-12-10 22:11 [PATCH 0/2 V3] nl80211/cfg80211: Support PMF on drivers with integrated " Chet Lanctot
2013-12-10 22:11 ` [PATCH 2/2 V3] nl80211/cfg80211: Enable station PMF requirement to be specified to driver with " Chet Lanctot
2013-12-16 14:26 ` 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=1389026403.5891.36.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 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).