From: Kalle Valo <kvalo@kernel.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: Arend van Spriel <aspriel@gmail.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
SHA-cyfmac-dev-list@infineon.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Arend van Spriel <arend.vanspriel@broadcom.com>,
Konrad Dybcio <konrad.dybcio@linaro.org>
Subject: Re: wifi: brcmfmac: pcie: Add 4359C0 firmware definition
Date: Mon, 6 Mar 2023 10:09:11 +0000 (UTC) [thread overview]
Message-ID: <167809735003.16730.2135671982947382285.kvalo@kernel.org> (raw)
In-Reply-To: <20230224-topic-brcm_tone-v1-1-333b0ac67934@linaro.org>
Konrad Dybcio <konrad.dybcio@linaro.org> wrote:
> Some phones from around 2016, as well as other random devices have
> this chip called 43956 or 4359C0 or 43596A0, which is more or less
> just a rev bump (v9) of the already-supported 4359. Add a corresponding
> firmware definition to allow for choosing the correct blob.
>
> Suggested-by: Arend van Spriel <arend.vanspriel@broadcom.com>
> Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
Patch applied to wireless-next.git, thanks.
e5c3da9abd44 wifi: brcmfmac: pcie: Add 4359C0 firmware definition
--
https://patchwork.kernel.org/project/linux-wireless/patch/20230224-topic-brcm_tone-v1-1-333b0ac67934@linaro.org/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2023-03-06 10:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 12:59 [PATCH] " Konrad Dybcio
2023-03-06 10:09 ` 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=167809735003.16730.2135671982947382285.kvalo@kernel.org \
--to=kvalo@kernel.org \
--cc=SHA-cyfmac-dev-list@infineon.com \
--cc=arend.vanspriel@broadcom.com \
--cc=aspriel@gmail.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=konrad.dybcio@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®