From: "Rafał Miłecki" <rafal@milecki.pl>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
"Kalle Valo" <kvalo@codeaurora.org>,
linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
brcm80211-dev-list@cypress.com
Subject: Re: [PATCH wireless-drivers-next 2/2] brcmfmac: print firmware reported general status errors
Date: Thu, 21 Feb 2019 12:13:21 +0100 [thread overview]
Message-ID: <01dbfeccc2e6f3fcd2e6bd4ccedf805a@milecki.pl> (raw)
In-Reply-To: <e644a5b7-c70d-056a-740e-997c931863c2@broadcom.com>
On 2019-02-21 11:45, Arend Van Spriel wrote:
> On 2/21/2019 11:33 AM, Rafał Miłecki wrote:
>> From: Rafał Miłecki <rafal@milecki.pl>
>>
>> Firmware may report general errors using a special message type. Add
>> basic support for it by simply decoding & printing an error number.
>>
>> A sample situation in which firmware reports a buf error:
>> CONSOLE: 027084.733 no host response IOCTL buffer available..so fail
>> the request
>> will now produce a "Firmware reported general error: 9" on the host.
>
> Could have meaningful message instead of a number. I can do that in
> follow up patch if you do not have the information.
That would be nice, thanks!
next prev parent reply other threads:[~2019-02-21 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 10:33 [PATCH wireless-drivers-next 1/2] brcmfmac: fix size of the struct msgbuf_ring_status Rafał Miłecki
2019-02-21 10:33 ` [PATCH wireless-drivers-next 2/2] brcmfmac: print firmware reported general status errors Rafał Miłecki
2019-02-21 10:45 ` Arend Van Spriel
2019-02-21 11:13 ` Rafał Miłecki [this message]
2019-02-28 8:28 ` [PATCH wireless-drivers-next 1/2] brcmfmac: fix size of the struct msgbuf_ring_status Kalle Valo
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=01dbfeccc2e6f3fcd2e6bd4ccedf805a@milecki.pl \
--to=rafal@milecki.pl \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211-dev-list@cypress.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@gmail.com \
/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.