From: Arend Van Spriel <arend.vanspriel@broadcom.com>
To: "Rafał Miłecki" <zajec5@gmail.com>, "Kalle Valo" <kvalo@codeaurora.org>
Cc: "Franky Lin" <franky.lin@broadcom.com>,
"Hante Meuleman" <hante.meuleman@broadcom.com>,
"Pieter-Paul Giesberts" <pieter-paul.giesberts@broadcom.com>,
"Franky Lin" <frankyl@broadcom.com>,
linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH] brcmfmac: update BRCMFMAC symbol description
Date: Wed, 22 Mar 2017 20:38:41 +0100 [thread overview]
Message-ID: <90f2fa7c-4bb7-7f1a-0641-19ff1e21e64c@broadcom.com> (raw)
In-Reply-To: <20170321144339.1709-1-zajec5@gmail.com>
On 21-3-2017 15:43, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> For quite some time now brcmfmac supports 802.11ac chipsets and it's
> not limited to embedded devices only. There are even standalone PCIe
> cards based on BCM43602 or BCM4366.
minor comments below.
Reviewed-by: Arend van Spriel <arend.vanspriel@broadcom.com>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
> drivers/net/wireless/broadcom/brcm80211/Kconfig | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/net/wireless/broadcom/brcm80211/Kconfig b/drivers/net/wireless/broadcom/brcm80211/Kconfig
> index d93561f6ef97..817cb28f518f 100644
> --- a/drivers/net/wireless/broadcom/brcm80211/Kconfig
> +++ b/drivers/net/wireless/broadcom/brcm80211/Kconfig
> @@ -18,14 +18,14 @@ config BRCMSMAC
> module, the driver will be called brcmsmac.ko.
>
> config BRCMFMAC
> - tristate "Broadcom IEEE802.11n embedded FullMAC WLAN driver"
> + tristate "Broadcom IEEE802.11n WLAN driver"
You still mention 11n. Let's drop the 'n' here or IEEE802.11n entirely
like below. Would like to keep the term FullMAC though.
Regards,
Arend
next prev parent reply other threads:[~2017-03-22 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 14:43 [PATCH] brcmfmac: update BRCMFMAC symbol description Rafał Miłecki
2017-03-22 19:38 ` Arend Van Spriel [this message]
2017-03-22 20:27 ` Rafał Miłecki
2017-03-23 10:29 ` [PATCH V2] " Rafał Miłecki
2017-04-05 12:35 ` [V2] " 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=90f2fa7c-4bb7-7f1a-0641-19ff1e21e64c@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=franky.lin@broadcom.com \
--cc=frankyl@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pieter-paul.giesberts@broadcom.com \
--cc=rafal@milecki.pl \
--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.