The patch is dropped, but I still owe you a response to this. I missed it because you sent 2 or 3 replies confusing me.

On 05/20/15 17:02, Rafał Miłecki wrote:
On 20 May 2015 at 14:09, Arend van Spriel<[email protected]>  wrote:
@@ -139,11 +165,11 @@ brcmf_nvram_handle_value(struct nvram_parser *nvp)
         char *ekv;
         u32 cplen;

-       c = nvp->fwnv->data[nvp->pos];
-       if (!is_nvram_char(c)) {
+       c = nvp->data[nvp->pos];
+       if (!is_nvram_char(c)&&  (c != ' ')) {

Don't smuggle behavior changes in patches doing something else!

The subject is "Add support for host platform NVRAM loading" and guess what. That type of NVRAM turned out to have spaces in the entries so in my opinion it is related to this patch. I can split it up if you feel strongly about this.

@@ -406,19 +434,34 @@ static void brcmf_fw_request_nvram_done(const struct 
firmware *fw, void *ctx)
         struct brcmf_fw *fwctx = ctx;
         u32 nvram_length = 0;
         void *nvram = NULL;
+       u8 *data = NULL;
+       size_t data_len;
+       bool raw_nvram;

         brcmf_dbg(TRACE, "enter: dev=%s\n", dev_name(fwctx->dev));
-       if (!fw&&  !(fwctx->flags&  BRCMF_FW_REQ_NV_OPTIONAL))
-               goto fail;
+       if ((fw)&&  (fw->data)) {

if (fw&&  fw->data)
will work just fine, I'm surprised checkpatch doesn't complain.

I ran checkpatch.pl --strict and did not get complaint about this change.

Regards,
Arend
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to