From: Arend van Spriel <arend@broadcom.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Kalle Valo <kvalo@codeaurora.org>,
<linux-wireless@vger.kernel.org>,
Brett Rudley <brudley@broadcom.com>,
"Franky (Zhenhui) Lin" <frankyl@broadcom.com>,
Hante Meuleman <meuleman@broadcom.com>,
<brcm80211-dev-list@broadcom.com>
Subject: Re: [PATCH] brcmfmac: check result of USB firmware request
Date: Fri, 8 May 2015 11:30:28 +0200 [thread overview]
Message-ID: <554C8234.4010402@broadcom.com> (raw)
In-Reply-To: <1431000783-17411-1-git-send-email-zajec5@gmail.com>
On 05/07/15 14:13, Rafał Miłecki wrote:
> This prevents silence failures with driver waiting (infinitely) for a
> callback.
Looks like proper thing to do :-p
Acked-by: Arend van Spriel <arend@broadcom.com>
> Signed-off-by: Rafał Miłecki<zajec5@gmail.com>
> ---
> I don't really have any opinion if this should go for next or as a fix.
> ---
> drivers/net/wireless/brcm80211/brcmfmac/usb.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/wireless/brcm80211/brcmfmac/usb.c b/drivers/net/wireless/brcm80211/brcmfmac/usb.c
> index 5df6aa7..daba86d 100644
> --- a/drivers/net/wireless/brcm80211/brcmfmac/usb.c
> +++ b/drivers/net/wireless/brcm80211/brcmfmac/usb.c
> @@ -1270,8 +1270,13 @@ static int brcmf_usb_probe_cb(struct brcmf_usbdev_info *devinfo)
> bus->chiprev = bus_pub->chiprev;
>
> /* request firmware here */
> - brcmf_fw_get_firmwares(dev, 0, brcmf_usb_get_fwname(devinfo), NULL,
> - brcmf_usb_probe_phase2);
> + ret = brcmf_fw_get_firmwares(dev, 0, brcmf_usb_get_fwname(devinfo),
> + NULL, brcmf_usb_probe_phase2);
> + if (ret) {
> + brcmf_err("firmware request failed: %d\n", ret);
> + goto fail;
> + }
> +
> return 0;
>
> fail:
next prev parent reply other threads:[~2015-05-08 9:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 12:13 [PATCH] brcmfmac: check result of USB firmware request Rafał Miłecki
2015-05-08 9:30 ` Arend van Spriel [this message]
2015-05-09 13:59 ` Kalle Valo
2015-05-09 14:02 ` 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=554C8234.4010402@broadcom.com \
--to=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=brudley@broadcom.com \
--cc=frankyl@broadcom.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=meuleman@broadcom.com \
--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.