From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Dan Haab <riproute@gmail.com>, Kalle Valo <kvalo@codeaurora.org>
Cc: Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
Chi-Hsien Lin <chi-hsien.lin@cypress.com>,
Wright Feng <wright.feng@cypress.com>,
Double Lo <double.lo@cypress.com>,
Pieter-Paul Giesberts <pieter-paul.giesberts@broadcom.com>,
Chung-Hsien Hsu <stanley.hsu@cypress.com>,
linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
brcm80211-dev-list@cypress.com, Dan Haab <dhaab@luxul.com>,
Dan Haab <dan.haab@luxul.com>
Subject: Re: [PATCH] brcmfmac: add support for BCM4366E chipset
Date: Fri, 23 Mar 2018 10:31:50 +0100 [thread overview]
Message-ID: <5AB4C986.1090709@broadcom.com> (raw)
In-Reply-To: <1521734286-16293-1-git-send-email-dan.haab@luxul.com>
On 3/22/2018 4:58 PM, Dan Haab wrote:
> From: Dan Haab <dhaab@luxul.com>
>
> BCM4366E is a wireless chipset with a BCM43664 ChipCommon. It's
> supported by the same firmware as 4366c0.
Thanks, Dan
I have a patch for that queued up already. So let me push that instead.
Regards,
Arend
next prev parent reply other threads:[~2018-03-23 9:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 15:58 [PATCH] brcmfmac: add support for BCM4366E chipset Dan Haab
2018-03-23 9:31 ` Arend van Spriel [this message]
2018-03-30 7:26 ` Rafał Miłecki
2018-04-03 8:22 ` Arend van Spriel
2018-04-03 10:17 ` Rafał Miłecki
2018-04-03 11:24 ` Arend van Spriel
2018-04-03 11:46 ` Rafał Miłecki
-- strict thread matches above, loose matches on Subject: below --
2018-04-03 8:21 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=5AB4C986.1090709@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211-dev-list@cypress.com \
--cc=chi-hsien.lin@cypress.com \
--cc=dan.haab@luxul.com \
--cc=dhaab@luxul.com \
--cc=double.lo@cypress.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pieter-paul.giesberts@broadcom.com \
--cc=riproute@gmail.com \
--cc=stanley.hsu@cypress.com \
--cc=wright.feng@cypress.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.