From: zijuhu@codeaurora.org
To: Josh Boyer <jwboyer@kernel.org>
Cc: Linux Firmware <linux-firmware@kernel.org>,
Rocky Liao <rjliao@codeaurora.org>,
tjiang@codeaurora.org, Zijun Hu <quic_zijuhu@quicinc.com>
Subject: Re: QCA Bluetooth WCN685x firmware pull request at 2022/01/04
Date: Thu, 13 Jan 2022 16:12:49 +0800 [thread overview]
Message-ID: <7c078a1a6a9d5d834b30f252706e517e@codeaurora.org> (raw)
In-Reply-To: <CA+5PVA4qFX3Gv_kuWEpe_mof=PE0CGuK4WE3bbbyCkDpPabDFg@mail.gmail.com>
On 2022-01-07 20:26, Josh Boyer wrote:
> On Tue, Jan 4, 2022 at 4:36 AM Zijun Hu <zijuhu@codeaurora.org> wrote:
>>
>> Hi linux-firmware maintainers,
>>
>> Here's a pull request for btqca bluetooth driver. Please let me know
>> if you have any problems.
>>
>> The following changes since commit
>> commit 57d6b9507e28ac4803ea4aa4dba9592c889d6733
>> cnm: add chips&media wave521c firmware. (Mon Dec 27 09:07:08 2021
>> +0000)
>>
>> are available in the Git repository at:
>>
>> https://github.com/zijun-hu/qca-btfw.git
>>
>> for you to fetch changes up to
>> 17fe7809058ad5949c12d80bf446e726f9e9f782:
>> ----------------------------------------------------------------
>> Zijun Hu (1):
>> QCA: Add Bluetooth nvm file for WCN685x (Tue Jan 4 14:14:51
>> 2022 +0800)
>
> There are actually 3 commits on your main branch that will be merged,
> not just this one. They are:
>
> 17fe7809058ad5949c12d80bf446e726f9e9f782 QCA: Add Bluetooth nvm file
> for WCN685x
> 72af07ecad7646f84e49222596ad09bcebe223d9 QCA: Update Bluetooth WCN685x
> 2.1 firmware to 2.1.0-00324
> 7411d2bf5afa895c6440ca2f935a50a74245eee7 QCA: Update Bluetooth WCN685x
> 2.0 firmware to 2.0.0-00609
>
> Is that what you wanted with this pull request?
yes, there are 3 commits to merge.
thank you
>
> josh
next prev parent reply other threads:[~2022-01-13 8:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 9:36 QCA Bluetooth WCN685x firmware pull request at 2022/01/04 Zijun Hu
2022-01-07 12:26 ` Josh Boyer
2022-01-13 8:12 ` zijuhu [this message]
2022-01-18 14:44 ` 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=7c078a1a6a9d5d834b30f252706e517e@codeaurora.org \
--to=zijuhu@codeaurora.org \
--cc=jwboyer@kernel.org \
--cc=linux-firmware@kernel.org \
--cc=quic_zijuhu@quicinc.com \
--cc=rjliao@codeaurora.org \
--cc=tjiang@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