From: Arend Van Spriel <arend.vanspriel@broadcom.com>
To: Wright Feng <wright.feng@cypress.com>,
franky.lin@broadcom.com, hante.meuleman@broadcom.com,
kvalo@codeaurora.org, chi-hsien.lin@cypress.com
Cc: linux-wireless@vger.kernel.org, brcm80211-dev-list.pdl@broadcom.com
Subject: Re: [PATCH 2/3] brcmfmac: make firmware eap_restrict a module parameter
Date: Thu, 19 Mar 2020 09:28:06 +0100 [thread overview]
Message-ID: <aa29c77c-cfe4-3d71-1860-f9bcb9e0282b@broadcom.com> (raw)
In-Reply-To: <1584604406-15452-3-git-send-email-wright.feng@cypress.com>
On 3/19/2020 8:53 AM, Wright Feng wrote:
> When eap_restrict is enabled, firmware will toss non-802.1x frames from
> tx/rx data path if station not yet authorized.
> Internal firmware eap_restrict is disabled by default. This patch makes
> it possible to enable firmware eap_restrict by specifying
> eap_restrict=1 as module parameter.
What is the reason for not having this toss behavior as default? Don't
see much reason for having the module parameter.
> Signed-off-by: Wright Feng <wright.feng@cypress.com>
> Signed-off-by: Chi-hsien Lin <chi-hsien.lin@cypress.com>
> ---
> drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c | 9 +++++++++
> drivers/net/wireless/broadcom/brcm80211/brcmfmac/common.c | 5 +++++
> drivers/net/wireless/broadcom/brcm80211/brcmfmac/common.h | 2 ++
> 3 files changed, 16 insertions(+)
next prev parent reply other threads:[~2020-03-19 8:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 7:53 [PATCH 0/3] Add AP isolate support and two modules parameters Wright Feng
2020-03-19 7:53 ` [PATCH 1/3] brcmfmac: support AP isolate Wright Feng
2020-03-19 8:48 ` Arend Van Spriel
2020-03-20 8:04 ` Wright Feng
2020-03-19 7:53 ` [PATCH 2/3] brcmfmac: make firmware eap_restrict a module parameter Wright Feng
2020-03-19 8:28 ` Arend Van Spriel [this message]
2020-03-20 8:06 ` Wright Feng
2020-03-22 14:29 ` Kalle Valo
2020-03-19 7:53 ` [PATCH 3/3] brcmfmac: make setting SDIO workqueue WQ_HIGHPRI " Wright Feng
2020-03-19 8:55 ` Arend Van Spriel
2020-03-20 8:08 ` Wright Feng
2020-03-20 8:18 ` Arend Van Spriel
2020-03-20 9:01 ` Wright Feng
2020-03-24 18:23 ` Tejun Heo
2020-03-25 4:29 ` Wright Feng
2020-03-25 14:08 ` Tejun Heo
2020-03-25 14:53 ` Arend Van Spriel
2020-03-25 15:06 ` Wright Feng
2020-03-25 15:12 ` Tejun Heo
2020-03-27 9:14 ` Wright Feng
2020-04-03 14:59 ` Tejun Heo
2020-03-25 15:10 ` Tejun Heo
2020-03-22 14:32 ` Kalle Valo
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=aa29c77c-cfe4-3d71-1860-f9bcb9e0282b@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=chi-hsien.lin@cypress.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=wright.feng@cypress.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).