From: Kalle Valo <kvalo@codeaurora.org>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>
Cc: linux-wireless@vger.kernel.org,
Arend van Spriel <arend.vanspriel@broadcom.com>
Subject: Re: [1/6] brcmfmac: check p2pdev mac address uniqueness
Date: Mon, 30 Apr 2018 10:42:08 +0000 (UTC) [thread overview]
Message-ID: <20180430104208.EC5FE607CF@smtp.codeaurora.org> (raw)
In-Reply-To: <1524737811-1965-1-git-send-email-arend.vanspriel@broadcom.com>
Arend Van Spriel <arend.vanspriel@broadcom.com> wrote:
> The mac address for p2pdev must be different from the primary interface
> due to firmware requirement. Add an explicit check for this requirement
> if user-space provides a mac address.
>
> 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>
Patch applied to wireless-drivers-next.git, thanks.
cb746e47837a brcmfmac: check p2pdev mac address uniqueness
--
https://patchwork.kernel.org/patch/10365333/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2018-04-30 10:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 10:16 [PATCH 1/6] brcmfmac: check p2pdev mac address uniqueness Arend van Spriel
2018-04-26 10:16 ` [PATCH 3/6] brcmfmac: use nl80211_band directly to get ieee80211 channel Arend van Spriel
2018-04-30 10:43 ` [3/6] " Kalle Valo
2018-04-26 10:16 ` [PATCH 4/6] brcmfmac: constify firmware mapping tables Arend van Spriel
2018-04-26 10:16 ` [PATCH 5/6] brcmfmac: add hostready indication Arend van Spriel
2018-04-26 10:16 ` [PATCH 6/6] brcmfmac: coarse support for PCIe shared structure rev7 Arend van Spriel
2018-04-30 10:42 ` Kalle Valo [this message]
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=20180430104208.EC5FE607CF@smtp.codeaurora.org \
--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.