From: Kalle Valo <kvalo@codeaurora.org>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/8] brcmfmac: coredump functionality and fixes
Date: Tue, 15 May 2018 12:32:02 +0300 [thread overview]
Message-ID: <877eo5p8ml.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1526375691-31789-1-git-send-email-arend.vanspriel@broadcom.com> (Arend van Spriel's message of "Tue, 15 May 2018 11:14:43 +0200")
Arend van Spriel <arend.vanspriel@broadcom.com> writes:
> 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.
So what I'm planning to do is apply patch 1 now to fix the warning, send
a pull request to Dave and then fast forward w-d-next so that I can
apply rest of the patches.
--
Kalle Valo
next prev parent reply other threads:[~2018-05-15 9:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 9:14 [PATCH 0/8] brcmfmac: coredump functionality and fixes Arend van Spriel
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 ` Kalle Valo [this message]
2018-05-15 9:58 ` [PATCH 0/8] brcmfmac: coredump functionality and fixes 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=877eo5p8ml.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=arend.vanspriel@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 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.