From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless@vger.kernel.org,
Arend van Spriel <arend.vanspriel@broadcom.com>
Subject: [PATCH 0/8] brcmfmac: coredump functionality and fixes
Date: Tue, 15 May 2018 11:14:43 +0200 [thread overview]
Message-ID: <1526375691-31789-1-git-send-email-arend.vanspriel@broadcom.com> (raw)
This series is intended for 4.18:
* fix variable initialization found by kbuild bot.
* make ALLFFMAC variable static.
* support user-space initiated coredump.
The first two patches in this series apply to the master branch of the
wireless-drivers-next repository. The remaining patches related to coredump
functionality are dependent upon a commit present since v4.17-rc3:
commit ed4564babeeee4fb19fe4ec0beabe29754e380f9
Author: Arend van Spriel <aspriel@gmail.com>
Date: Sun Apr 8 23:57:07 2018 +0200
drivers: change struct device_driver::coredump() return type to void
Both w-d-next and bt-next (for patch 5/8) do not carry this patch yet.
Arend van Spriel (4):
brcmfmac: move ALLFFMAC variable in flowring module
brcmfmac: add support for sysfs initiated coredump
mwifiex: support sysfs initiated device coredump
btmrvl: support sysfs initiated firmware coredump
Franky Lin (4):
brcmfmac: fix initialization of struct cfg80211_inform_bss variable
brcmfmac: validate user provided data for memdump before copying
brcmfmac: trigger memory dump upon firmware halt signal
brcmfmac: trigger memory dump on SDIO firmware halt message
drivers/bluetooth/btmrvl_debugfs.c | 31 ----------------------
drivers/bluetooth/btmrvl_drv.h | 2 --
drivers/bluetooth/btmrvl_main.c | 6 -----
drivers/bluetooth/btmrvl_sdio.c | 11 +++++---
.../wireless/broadcom/brcm80211/brcmfmac/bcmsdh.c | 1 +
.../net/wireless/broadcom/brcm80211/brcmfmac/bus.h | 2 ++
.../broadcom/brcm80211/brcmfmac/cfg80211.c | 2 +-
.../wireless/broadcom/brcm80211/brcmfmac/common.c | 2 --
.../wireless/broadcom/brcm80211/brcmfmac/common.h | 2 --
.../wireless/broadcom/brcm80211/brcmfmac/core.c | 8 ++++++
.../wireless/broadcom/brcm80211/brcmfmac/debug.c | 3 ++-
.../broadcom/brcm80211/brcmfmac/flowring.c | 2 ++
.../wireless/broadcom/brcm80211/brcmfmac/pcie.c | 6 +++++
.../wireless/broadcom/brcm80211/brcmfmac/sdio.c | 4 ++-
drivers/net/wireless/marvell/mwifiex/debugfs.c | 31 +---------------------
drivers/net/wireless/marvell/mwifiex/pcie.c | 18 +++++++++++--
drivers/net/wireless/marvell/mwifiex/sdio.c | 12 +++++++++
drivers/net/wireless/marvell/mwifiex/usb.c | 13 +++++++++
18 files changed, 75 insertions(+), 81 deletions(-)
--
1.9.1
next reply other threads:[~2018-05-15 9:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 9:14 Arend van Spriel [this message]
2018-05-15 9:14 ` [PATCH 1/8] brcmfmac: fix initialization of struct cfg80211_inform_bss variable Arend van Spriel
2018-05-15 15:09 ` [1/8] " Kalle Valo
2018-05-15 9:14 ` [PATCH 2/8] brcmfmac: move ALLFFMAC variable in flowring module Arend van Spriel
2018-05-15 9:14 ` [PATCH 3/8] brcmfmac: add support for sysfs initiated coredump Arend van Spriel
2018-05-15 9:14 ` [PATCH 4/8] mwifiex: support sysfs initiated device coredump Arend van Spriel
2018-05-15 20:22 ` kbuild test robot
2018-05-16 8:55 ` Arend van Spriel
2018-05-16 9:22 ` Kalle Valo
2018-05-15 9:14 ` [PATCH 5/8] btmrvl: support sysfs initiated firmware coredump Arend van Spriel
2018-05-15 9:30 ` Kalle Valo
2018-05-15 9:57 ` Arend van Spriel
2018-05-15 10:02 ` Kalle Valo
2018-05-15 10:02 ` Kalle Valo
2018-05-15 10:37 ` Arend van Spriel
2018-05-15 9:14 ` [PATCH 6/8] brcmfmac: validate user provided data for memdump before copying Arend van Spriel
2018-05-15 9:14 ` [PATCH 7/8] brcmfmac: trigger memory dump upon firmware halt signal Arend van Spriel
2018-05-15 9:14 ` [PATCH 8/8] brcmfmac: trigger memory dump on SDIO firmware halt message Arend van Spriel
2018-05-15 9:32 ` [PATCH 0/8] brcmfmac: coredump functionality and fixes Kalle Valo
2018-05-15 9:58 ` Arend van Spriel
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=1526375691-31789-1-git-send-email-arend.vanspriel@broadcom.com \
--to=arend.vanspriel@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 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.