From: Arend van Spriel <arend@broadcom.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Arend van Spriel <arend@broadcom.com>
Subject: [PATCH 0/8] brcmfmac: event handling and other fixes
Date: Mon, 11 Apr 2016 11:35:20 +0200 [thread overview]
Message-ID: <1460367328-12082-1-git-send-email-arend@broadcom.com> (raw)
This series provides the following:
* avoid unexpected firmware events.
* allow passing events explicitly for PCIe and SDIO devices.
* fix issue with boardrev entry in nvram.
* fix for wowl.
* fix possible null pointer access upon aborting p2p scan.
The series is intended for v4.7 kernel and applies to the master
branch of the wireless-drivers-next repository.
Arend van Spriel (3):
brcmfmac: cleanup ampdu-rx host reorder code
brcmfmac: revise handling events in receive path
brcmfmac: create common function for handling brcmf_proto_hdrpull()
Franky Lin (1):
brcmfmac: screening firmware event packet
Hante Meuleman (4):
brcmfmac: clear eventmask array before using it
brcmfmac: fix clearing wowl wake indicators
brcmfmac: insert default boardrev in nvram data if missing
brcmfmac: fix p2p scan abort null pointer exception
.../wireless/broadcom/brcm80211/brcmfmac/bcdc.c | 7 +
.../net/wireless/broadcom/brcm80211/brcmfmac/bus.h | 4 +-
.../broadcom/brcm80211/brcmfmac/cfg80211.c | 3 +-
.../wireless/broadcom/brcm80211/brcmfmac/core.c | 247 +++------------------
.../wireless/broadcom/brcm80211/brcmfmac/core.h | 4 -
.../broadcom/brcm80211/brcmfmac/firmware.c | 30 ++-
.../wireless/broadcom/brcm80211/brcmfmac/fweh.c | 1 +
.../broadcom/brcm80211/brcmfmac/fwsignal.c | 209 +++++++++++++++++
.../broadcom/brcm80211/brcmfmac/fwsignal.h | 1 +
.../wireless/broadcom/brcm80211/brcmfmac/msgbuf.c | 46 ++--
.../net/wireless/broadcom/brcm80211/brcmfmac/p2p.c | 2 +-
.../wireless/broadcom/brcm80211/brcmfmac/proto.h | 16 ++
.../wireless/broadcom/brcm80211/brcmfmac/sdio.c | 32 ++-
.../net/wireless/broadcom/brcm80211/brcmfmac/usb.c | 2 +-
14 files changed, 352 insertions(+), 252 deletions(-)
--
1.9.1
next reply other threads:[~2016-04-11 9:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 9:35 Arend van Spriel [this message]
2016-04-11 9:35 ` [PATCH 1/8] brcmfmac: clear eventmask array before using it Arend van Spriel
2016-04-14 13:01 ` [1/8] " Kalle Valo
2016-04-11 9:35 ` [PATCH 2/8] brcmfmac: fix clearing wowl wake indicators Arend van Spriel
2016-04-11 9:35 ` [PATCH 3/8] brcmfmac: insert default boardrev in nvram data if missing Arend van Spriel
2016-04-16 8:15 ` Rafał Miłecki
2016-04-11 9:35 ` [PATCH 4/8] brcmfmac: fix p2p scan abort null pointer exception Arend van Spriel
2016-04-11 9:35 ` [PATCH 5/8] brcmfmac: screening firmware event packet Arend van Spriel
2016-04-11 9:35 ` [PATCH 6/8] brcmfmac: cleanup ampdu-rx host reorder code Arend van Spriel
2016-04-11 9:35 ` [PATCH 7/8] brcmfmac: revise handling events in receive path Arend van Spriel
2016-04-25 10:00 ` Rafał Miłecki
2016-04-25 10:40 ` Rafał Miłecki
2016-04-11 9:35 ` [PATCH 8/8] brcmfmac: create common function for handling brcmf_proto_hdrpull() Arend van Spriel
2016-04-11 11:20 ` [PATCH 0/8] brcmfmac: event handling and other fixes Rafał Miłecki
2016-04-12 8:55 ` Arend van Spriel
2016-04-12 11:49 ` Julian Calaby
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=1460367328-12082-1-git-send-email-arend@broadcom.com \
--to=arend@broadcom.com \
--cc=kvalo@codeaurora.org \
--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).