From: Kalle Valo <kvalo@codeaurora.org>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>
Cc: linux-wireless@vger.kernel.org,
Arend van Spriel <arend.vanspriel@broadcom.com>
Subject: Re: [for-4.16, V3, 1/2] brcmfmac: add possibility to obtain firmware error
Date: Wed, 7 Mar 2018 14:37:52 +0000 (UTC) [thread overview]
Message-ID: <20180307143752.4390660398@smtp.codeaurora.org> (raw)
In-Reply-To: <1519848920-18000-2-git-send-email-arend.vanspriel@broadcom.com>
Arend Van Spriel <arend.vanspriel@broadcom.com> wrote:
> The feature module needs to evaluate the actual firmware error return
> upon a control command. This adds a flag to struct brcmf_if that the
> caller can set. This flag is checked to determine the error code that
> needs to be returned.
>
> Fixes: b69c1df47281 ("brcmfmac: separate firmware errors from i/o errors")
> Reviewed-by: Hante Meuleman <hante.meuleman@broadcom.com>
> Reviewed-by: Pieter-Paul Giesberts <pieter-paul.giesberts@broadcom.com>
> Reviewed-by: Franky Lin <franky.lin@broadcom.com>
> Signed-off-by: Arend van Spriel <arend.vanspriel@broadcom.com>
2 patches applied to wireless-drivers.git, thanks.
933897342d07 brcmfmac: add possibility to obtain firmware error
455f3e76cfc0 brcmfmac: fix P2P_DEVICE ethernet address generation
--
https://patchwork.kernel.org/patch/10249603/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2018-03-07 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 20:15 [PATCH for-4.16 V3 0/2] brcmfmac: small fixes Arend van Spriel
2018-02-28 20:15 ` [PATCH for-4.16 V3 1/2] brcmfmac: add possibility to obtain firmware error Arend van Spriel
2018-03-07 14:37 ` Kalle Valo [this message]
2018-02-28 20:15 ` [PATCH for-4.16 V3 2/2] brcmfmac: fix P2P_DEVICE ethernet address generation 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=20180307143752.4390660398@smtp.codeaurora.org \
--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 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).