MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
Date:   Thu, 21 Feb 2019 12:13:21 +0100
From:   =?UTF-8?Q?Rafa=C5=82_Mi=C5=82ecki?= <rafal@milecki.pl>
To:     Arend Van Spriel <arend.vanspriel@broadcom.com>
Cc:     =?UTF-8?Q?Rafa=C5=82_Mi=C5=82ecki?= <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
In-Reply-To: <e644a5b7-c70d-056a-740e-997c931863c2@broadcom.com>
References: <20190221103325.28228-1-zajec5@gmail.com>
 <20190221103325.28228-2-zajec5@gmail.com>
 <e644a5b7-c70d-056a-740e-997c931863c2@broadcom.com>
Message-ID: <01dbfeccc2e6f3fcd2e6bd4ccedf805a@milecki.pl>
User-Agent: Roundcube Webmail/1.3.8
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk

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!