From: Josh Boyer <jwboyer@kernel.org>
To: Balakrishna Godavarthi <bgodavar@codeaurora.org>
Cc: Linux Firmware <linux-firmware@kernel.org>,
mka@chromium.org,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
BlueZ development <linux-bluetooth@vger.kernel.org>,
Hemantg <hemantg@codeaurora.org>,
Linux-arm Msm <linux-arm-msm@vger.kernel.org>,
gubbaven@codeaurora.org
Subject: Re: Firmware files for QCA BT chip WCN3991.
Date: Mon, 24 Feb 2020 07:33:34 -0500 [thread overview]
Message-ID: <CA+5PVA4rXyvK=77mqxVPdvD4iUuqZHCt6CwwspG4K5FssfLxZA@mail.gmail.com> (raw)
In-Reply-To: <b69f21863b936c2407d2e22dcd258013@codeaurora.org>
On Fri, Feb 21, 2020 at 8:15 AM <bgodavar@codeaurora.org> wrote:
>
> + Josh boyer to pick the firmware
>
> On 2020-02-20 16:05, bgodavar@codeaurora.org wrote:
> > Hi,
> >
> > The following changes since commit
> > 54b017d06a44bfd9b4c2757cace6cc349afd5bf2:
> >
> > qca: Add firmware files for BT chip wcn3991. (2020-02-20 16:01:04
> > +0530)
> >
> > are available in the Git repository at:
> >
> > https://github.com/bgodavar/qca_bt_wcn3991.git
> >
> > for you to fetch changes up to
> > 54b017d06a44bfd9b4c2757cace6cc349afd5bf2:
> >
> > qca: Add firmware files for BT chip wcn3991. (2020-02-20 16:01:04
> > +0530)
Pulled and pushed out.
josh
prev parent reply other threads:[~2020-02-24 12:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 10:35 Firmware files for QCA BT chip WCN3991 bgodavar
2020-02-20 10:35 ` bgodavar
2020-02-20 10:35 ` bgodavar
2020-02-20 10:35 ` bgodavar
2020-02-21 13:15 ` bgodavar
2020-02-21 13:15 ` bgodavar
2020-02-21 13:15 ` bgodavar
2020-02-21 13:15 ` bgodavar
2020-02-24 12:33 ` 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+5PVA4rXyvK=77mqxVPdvD4iUuqZHCt6CwwspG4K5FssfLxZA@mail.gmail.com' \
--to=jwboyer@kernel.org \
--cc=bgodavar@codeaurora.org \
--cc=gubbaven@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 \
--cc=mka@chromium.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).