From: Arend van Spriel <arend@broadcom.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Kalle Valo <kvalo@codeaurora.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
Hante Meuleman <meuleman@broadcom.com>
Subject: Re: [PATCH v2 1/7] brcmfmac: Add support for host platform NVRAM loading.
Date: Thu, 20 Aug 2015 18:14:09 +0200 [thread overview]
Message-ID: <55D5FCD1.2070304@broadcom.com> (raw)
In-Reply-To: <CACna6rw9o3_mG3ZoDuRoBmVpVKuso52KXeeHr6R8nDotD4mwPQ@mail.gmail.com>
On 08/20/2015 05:59 PM, Rafał Miłecki wrote:
> On 19 August 2015 at 23:21, Arend van Spriel <arend@broadcom.com> wrote:
>> subject changed to v2. So let's go over your beef.
>
> I really hope none of my comment was mean or anything :)
>
>
>> On 07/11/2015 07:09 PM, Rafał Miłecki wrote:
>>>
>>> On 10 July 2015 at 20:31, Arend van Spriel <arend@broadcom.com> wrote:
>>>> + data_len = fw->size;
>>>> + raw_nvram = false;
>>>> + } else {
>>>> + data = bcm47xx_nvram_get_contents(&data_len);
>>>> + if (!data && !(fwctx->flags & BRCMF_FW_REQ_NV_OPTIONAL))
>>>> + goto fail;
>>>> + raw_nvram = true;
>>>> + }
>>>>
>>>> - if (fw) {
>>>> - nvram = brcmf_fw_nvram_strip(fw->data, fw->size,
>>>> &nvram_length,
>>>> + if (data) {
>>>> + nvram = brcmf_fw_nvram_strip(data, data_len,
>>>> &nvram_length,
>>>> fwctx->domain_nr,
>>>> fwctx->bus_nr);
>>>> - release_firmware(fw);
>>>> - if (!nvram && !(fwctx->flags & BRCMF_FW_REQ_NV_OPTIONAL))
>>>> - goto fail;
>>>> + if (raw_nvram)
>>>> + bcm47xx_nvram_release_contents(data);
>>>
>>>
>>> This is cosmetical but maybe you could move above 2 lines next to the
>>> release_firmware? So we have all freeing code at one please? Do you
>>> think it would improve readability?
>>> Nothing important thought. Feel free to ignore me here.
>>
>>
>> confused! The release_firmware call is removed here, right?
>
> Yes, you removed it from the "if (data) {" condition body but also
> re-added right after it. AFAIR I got an impression it may make more
> sense to have something like:
> if (raw_nvram)
> bcm47xx_nvram_release_contents(data);
I did not check whether bcm47xx_nvram_release_contents deals with data
being NULL pointer. If so, I can change it.
Regards,
Arend
> if (fw)
> release_firmware(fw);
> but you can just ignore it if it doesn't sound clear.
>
next prev parent reply other threads:[~2015-08-20 16:14 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 18:31 [PATCH 0/7] brcmfmac: nvram loading and code rework Arend van Spriel
2015-07-10 18:31 ` [PATCH 1/7] brcmfmac: Add support for host platform NVRAM loading Arend van Spriel
2015-07-11 17:09 ` Rafał Miłecki
2015-08-19 21:21 ` [PATCH v2 " Arend van Spriel
2015-08-19 21:43 ` Arend van Spriel
2015-08-20 15:53 ` Rafał Miłecki
2015-08-20 16:06 ` Arend van Spriel
2015-08-20 16:21 ` Rafał Miłecki
2015-08-20 15:59 ` Rafał Miłecki
2015-08-20 16:14 ` Arend van Spriel [this message]
2015-07-10 18:31 ` [PATCH 2/7] brcmfmac: correct interface combination info Arend van Spriel
2015-07-10 18:31 ` [PATCH 3/7] brcmfmac: Increase nr of supported flowrings Arend van Spriel
2015-07-10 18:31 ` [PATCH 4/7] brcmfmac: add debugfs entry for msgbuf statistics Arend van Spriel
2015-07-10 18:31 ` [PATCH 5/7] brcmfmac: make use of cfg80211_check_combinations() Arend van Spriel
2015-07-10 18:31 ` [PATCH 6/7] brcmfmac: consolidate ifp lookup in driver core Arend van Spriel
2015-07-10 18:31 ` [PATCH 7/7] brcmfmac: block the correct flowring when backup queue overflow Arend van Spriel
2015-07-19 15:05 ` [PATCH 0/7] brcmfmac: nvram loading and code rework Rafał Miłecki
2015-07-20 17:14 ` Arend van Spriel
2015-07-23 16:02 ` Kalle Valo
2015-07-26 11:08 ` Arend van Spriel
2015-07-26 12:08 ` Kalle Valo
2015-07-26 15:40 ` Rafał Miłecki
2015-08-12 8:58 ` Arend van Spriel
2015-08-12 14:07 ` Rafał Miłecki
2015-08-19 14:58 ` Rafał Miłecki
2015-08-19 23:06 ` Rafał Miłecki
2015-08-20 10:23 ` Arend van Spriel
2015-08-20 15:51 ` Rafał Miłecki
2015-08-20 19:41 ` Arend van Spriel
-- strict thread matches above, loose matches on Subject: below --
2015-08-16 6:55 [PATCH V2 " Arend van Spriel
2015-08-16 6:55 ` [PATCH V2 1/7] brcmfmac: Add support for host platform NVRAM loading Arend van Spriel
2015-08-19 16:38 ` Rafał Miłecki
2015-08-19 20:55 ` Arend van Spriel
2015-08-20 19:50 ` Arend van Spriel
2015-08-24 19:28 ` 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=55D5FCD1.2070304@broadcom.com \
--to=arend@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 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).