From: Josh Boyer <jwboyer@kernel.org>
To: bgodavar@codeaurora.org
Cc: Linux Firmware <linux-firmware@kernel.org>,
BlueZ development <linux-bluetooth@vger.kernel.org>,
hemantg@codeaurora.org,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
linux-arm-msm@vger.kernel.org
Subject: Re: qca: update BT firmware files for QCA ROME chip.
Date: Mon, 1 Oct 2018 09:57:12 -0400 [thread overview]
Message-ID: <CA+5PVA4JQEwATu6ZR8H0vL04nyZzD5Cmnub-SSeJ1DNRpg7dww@mail.gmail.com> (raw)
In-Reply-To: <c56b472fa06e3a5e8127c2043c77305b@codeaurora.org>
On Mon, Oct 1, 2018 at 6:49 AM Balakrishna Godavarthi
<bgodavar@codeaurora.org> wrote:
>
> Hi,
>
> The following changes since commit
> 44d4fca9922a252a0bd81f6307bcc072a78da54a:
>
> Merge https://github.com/pmachata/linux-firmware (2018-09-13 11:45:40
> -0400)
>
> are available in the Git repository at:
>
> https://github.com/bgodavar/qca_rome_firmware master
>
> for you to fetch changes up to 534daf431c88b24236d23572039cdd79223b246a:
>
> qca: update BT firmware files for QCA ROME chip. (2018-09-18 13:11:47
> +0530)
>
> ----------------------------------------------------------------
> Balakrishna Godavarthi (1):
> qca: update BT firmware files for QCA ROME chip.
>
> qca/nvm_usb_00000302.bin | Bin 1953 -> 1996 bytes
> qca/rampatch_usb_00000302.bin | Bin 32940 -> 64168 bytes
> 2 files changed, 0 insertions(+), 0 deletions(-)
Pulled and pushed out.
Thanks.
josh
prev parent reply other threads:[~2018-10-01 13:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 10:49 qca: update BT firmware files for QCA ROME chip Balakrishna Godavarthi
2018-10-01 13:57 ` Josh Boyer [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=CA+5PVA4JQEwATu6ZR8H0vL04nyZzD5Cmnub-SSeJ1DNRpg7dww@mail.gmail.com \
--to=jwboyer@kernel.org \
--cc=bgodavar@codeaurora.org \
--cc=hemantg@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-firmware@kernel.org \
--cc=linux-kernel@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 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).