From: Kalle Valo <kvalo@codeaurora.org>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH V2 1/6] brcmfmac: move ALLFFMAC variable in flowring module
Date: Wed, 16 May 2018 16:36:22 +0300 [thread overview]
Message-ID: <87lgcjlo2x.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1526472723-15758-2-git-send-email-arend.vanspriel@broadcom.com> (Arend van Spriel's message of "Wed, 16 May 2018 14:11:58 +0200")
Arend van Spriel <arend.vanspriel@broadcom.com> writes:
> The only user of ALLFFMAC is the flowring module so no need to
> expose it in a header file.
>
> Reviewed-by: Hante Meuleman <hante.meuleman@broadcom.com>
> Reviewed-by: Pieter-Paul Giesberts <pieter-paul.giesberts@broadcom.com>
> Reviewed-by: Franky Lin <franky.lin@broadcom.com>
> Signed-off-by: Arend van Spriel <arend.vanspriel@broadcom.com>
> ---
> Hi Kalle,
>
> I recall Joe Perches posted patches dealing with broadcast address declarations,
> but don't know what happened with those. In patchwork [1] is says 'Not Applicable'
> whatever that means. I noticed Johannes set similar mac80211 change to
> 'Awaiting Upstream'. Anyway, when applying this patch the patch in [1] needs to
> be reworked.
>
> Regards,
> Arend
>
> [1] https://patchwork.kernel.org/patch/10318857/
'Not Applicable' means that I have assumed that the patch is not
suitable for my tree for whatever reason, I guess in this case because
it was part of a bigger patchset.
--
Kalle Valo
next prev parent reply other threads:[~2018-05-16 13:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 12:11 [PATCH V2 0/6] brcmfmac: coredump functionality and fixes Arend van Spriel
2018-05-16 12:11 ` [PATCH V2 1/6] brcmfmac: move ALLFFMAC variable in flowring module Arend van Spriel
2018-05-16 13:36 ` Kalle Valo [this message]
2018-05-23 15:54 ` [V2,1/6] " Kalle Valo
2018-05-16 12:11 ` [PATCH V2 2/6] brcmfmac: add support for sysfs initiated coredump Arend van Spriel
2018-05-16 12:12 ` [PATCH V2 3/6] mwifiex: support sysfs initiated device coredump Arend van Spriel
2018-05-16 13:50 ` Kalle Valo
2018-05-16 18:52 ` Arend van Spriel
2018-05-21 8:19 ` [EXT] " Ganapathi Bhat
2018-05-23 7:54 ` Kalle Valo
2018-05-23 8:11 ` Arend van Spriel
2018-05-23 8:17 ` Kalle Valo
2018-05-23 11:24 ` Ganapathi Bhat
2018-05-23 15:56 ` Kalle Valo
2018-05-16 12:12 ` [PATCH V2 4/6] brcmfmac: validate user provided data for memdump before copying Arend van Spriel
2018-05-16 12:12 ` [PATCH V2 5/6] brcmfmac: trigger memory dump upon firmware halt signal Arend van Spriel
2018-05-16 12:12 ` [PATCH V2 6/6] brcmfmac: trigger memory dump on SDIO firmware halt message Arend van Spriel
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=87lgcjlo2x.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=arend.vanspriel@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
/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.