From: Kalle Valo <kvalo@codeaurora.org>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Hante Meuleman <hante.meuleman@broadcom.com>,
Arend van Spriel <arend.vanspriel@broadcom.com>
Subject: Re: [1/9] brcmfmac: ignore 11d configuration errors
Date: Mon, 26 Sep 2016 17:38:01 +0000 (UTC) [thread overview]
Message-ID: <20160926173801.81A9F6159F@smtp.codeaurora.org> (raw)
In-Reply-To: <1474283399-14385-2-git-send-email-arend.vanspriel@broadcom.com>
Arend Van Spriel <arend.vanspriel@broadcom.com> wrote:
> From: Hante Meuleman <hante.meuleman@broadcom.com>
>
> 802.11d is not always supported by firmware anymore. Currently the
> AP configuration of 11d will cause an abort if the ioctl set is
> failing. This behavior is not correct and the error should be
> ignored.
>
> Reviewed-by: Arend Van Spriel <arend.vanspriel@broadcom.com>
> Reviewed-by: Franky Lin <franky.lin@broadcom.com>
> Reviewed-by: Pieter-Paul Giesberts <pieter-paul.giesberts@broadcom.com>
> Signed-off-by: Hante Meuleman <hante.meuleman@broadcom.com>
> Signed-off-by: Arend van Spriel <arend.vanspriel@broadcom.com>
9 patches applied to wireless-drivers-next.git, thanks.
b3589dfe0212 brcmfmac: ignore 11d configuration errors
704d1c6b56f4 brcmfmac: rework pointer trickery in brcmf_proto_bcdc_query_dcmd()
bc9816413601 brcmfmac: fix memory leak in brcmf_flowring_add_tdls_peer()
26305d3d7298 brcmfmac: initialize variable in brcmf_sdiod_regrl()
8fa5fdec09cd brcmfmac: remove worker from .ndo_set_mac_address() callback
835680b82f02 brcmfmac: remove unnecessary null pointer check
2b7425f3629b brcmfmac: fix clearing entry IPv6 address
a7ed7828ecda brcmfmac: fix out of bound access on clearing wowl wake indicator
92c313604711 brcmfmac: simplify mapping of auth type
--
https://patchwork.kernel.org/patch/9339033/
Documentation about submitting wireless patches and checking status
from patchwork:
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2016-09-26 17:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 11:09 [PATCH 0/9] brcmfmac: coverity fixes Arend van Spriel
2016-09-19 11:09 ` [PATCH 1/9] brcmfmac: ignore 11d configuration errors Arend van Spriel
2016-09-26 17:38 ` Kalle Valo [this message]
2016-09-19 11:09 ` [PATCH 2/9] brcmfmac: rework pointer trickery in brcmf_proto_bcdc_query_dcmd() Arend van Spriel
2016-09-19 11:09 ` [PATCH 3/9] brcmfmac: fix memory leak in brcmf_flowring_add_tdls_peer() Arend van Spriel
2016-09-19 11:09 ` [PATCH 4/9] brcmfmac: initialize variable in brcmf_sdiod_regrl() Arend van Spriel
2016-09-19 11:09 ` [PATCH 5/9] brcmfmac: remove worker from .ndo_set_mac_address() callback Arend van Spriel
2016-09-19 11:09 ` [PATCH 6/9] brcmfmac: remove unnecessary null pointer check Arend van Spriel
2016-09-19 11:09 ` [PATCH 7/9] brcmfmac: fix clearing entry IPv6 address Arend van Spriel
2016-09-19 11:09 ` [PATCH 8/9] brcmfmac: fix out of bound access on clearing wowl wake indicator Arend van Spriel
2016-09-19 11:09 ` [PATCH 9/9] brcmfmac: simplify mapping of auth type Arend van Spriel
2016-09-19 16:42 ` [PATCH 0/9] brcmfmac: coverity fixes Florian Fainelli
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=20160926173801.81A9F6159F@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=arend.vanspriel@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
/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).