From: Josh Boyer <jwboyer@kernel.org>
To: smagar@codeaurora.org
Cc: Linux Firmware <linux-firmware@kernel.org>,
mka@chromium.org,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
linux-bluethoth@vger.kernel.org,
Linux-arm Msm <linux-arm-msm@vger.kernel.org>,
Hemantg <hemantg@codeaurora.org>,
abhishekpandit@chromium.org,
Balakrishna Godavarthi <bgodavar@codeaurora.org>,
adhudase@codeaurora.org, sampnimm@codeaurora.org
Subject: Re: Request to update WCN3991 FW file
Date: Thu, 12 Aug 2021 09:22:00 -0400 [thread overview]
Message-ID: <CA+5PVA6q9ph=3nC4oDyHvuutqzMAqDjtTWahLN1xaZy=0sXJmQ@mail.gmail.com> (raw)
In-Reply-To: <0a05c2062052704d788511cf7edd874d@codeaurora.org>
Pulled and pushed out.
josh
On Thu, Aug 12, 2021 at 4:05 AM <smagar@codeaurora.org> wrote:
>
> Hi Team,
>
>
> Please include updated firmware bins for WCN3991. Change includes
> updated TLV file.
>
> Snapshot of pull request is as below, let me know if anything is
> missing.
>
>
>
> The following changes since commit
> 168452ee695b5edb9deb641059bc110b9c5e8fc7:
>
> Merge tag 'iwlwifi-fw-2021-07-19' of
> git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware
> into main (2021-07-19 14:35:47 -0400)
>
> are available in the git repository at:
>
> https://github.com/suraj714/linux-firmware-BT master
>
> for you to fetch changes up to 6a3a985022e1194045fc46a249ca29f8bf2fb427:
>
> QCA : Updated firmware files for WCN3991 (2021-08-12 10:03:49 +0530)
>
> ----------------------------------------------------------------
> smagar (1):
> QCA : Updated firmware files for WCN3991
>
> qca/crbtfw32.tlv | Bin 126772 -> 126036 bytes
> 1 file changed, 0 insertions(+), 0 deletions(-)
>
>
> Regards,
> Suraj Magar
next prev parent reply other threads:[~2021-08-12 13:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 8:05 Request to update WCN3991 FW file smagar
2021-08-12 13:22 ` Josh Boyer [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-05 7:06 Request to Update " asitshah
2020-11-05 7:06 ` asitshah
2020-11-13 15:17 ` Josh Boyer
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='CA+5PVA6q9ph=3nC4oDyHvuutqzMAqDjtTWahLN1xaZy=0sXJmQ@mail.gmail.com' \
--to=jwboyer@kernel.org \
--cc=abhishekpandit@chromium.org \
--cc=adhudase@codeaurora.org \
--cc=bgodavar@codeaurora.org \
--cc=hemantg@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluethoth@vger.kernel.org \
--cc=linux-firmware@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=sampnimm@codeaurora.org \
--cc=smagar@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).