linux-firmware.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
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,  abhishekpandit@chromium.org
Subject: Re: QCA: Add correct bin file for WCN3991
Date: Tue, 21 Jul 2020 07:31:29 -0400	[thread overview]
Message-ID: <CA+5PVA7P6bK12ZEUJEQb2cFntJuNSu99rF3TDCWmeep_XbLMQw@mail.gmail.com> (raw)
In-Reply-To: <6abd991d5d7d5175f5b7c6b168af770b@codeaurora.org>

On Thu, Jul 16, 2020 at 12:25 PM <bgodavar@codeaurora.org> wrote:
>
> The following changes since commit
> 3d3a06f720856cb897a8541951edd0b8f6f54a98:
>
>    linux-firmware: Update firmware file for Intel Bluetooth AX201
> (2020-07-13 07:51:54 -0400)
>
> are available in the git repository at:
>
>    https://github.com/bgodavar/qca_bt_fw/tree/qca_0714
>
> for you to fetch changes up to 3882702815e4b88bfd2f20b7eb66a3e85cbbb9b9:
>
>    QCA: Add correct bin file for WCN3991 (2020-07-14 11:00:13 +0530)
>
> ----------------------------------------------------------------
> Balakrishna Godavarthi (1):
>        QCA: Add correct bin file for WCN3991
>
>   qca/crnv32.bin | Bin 5299 -> 5299 bytes
>   1 file changed, 0 insertions(+), 0 deletions(-)

Pulled and pushed out.

josh

      parent reply	other threads:[~2020-07-21 11:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16 16:25 QCA: Add correct bin file for WCN3991 bgodavar
2020-07-16 16:25 ` bgodavar
2020-07-16 16:25 ` bgodavar
2020-07-16 16:25 ` bgodavar
2020-07-21 11:31 ` 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+5PVA7P6bK12ZEUJEQb2cFntJuNSu99rF3TDCWmeep_XbLMQw@mail.gmail.com \
    --to=jwboyer@kernel.org \
    --cc=abhishekpandit@chromium.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).