From: Ben Hutchings <ben@decadent.org.uk>
To: Vinod Koul <vinod.koul@intel.com>, linux-firmware@kernel.org
Cc: Patches Audio <patches.audio@intel.com>, alsa-devel@alsa-project.org
Subject: Re: [GIT PULL]: Geminilake audio firmware update
Date: Thu, 23 Nov 2017 01:49:08 +0000 [thread overview]
Message-ID: <1511401748.14687.14.camel@decadent.org.uk> (raw)
In-Reply-To: <20171107050032.GS3187@localhost>
[-- Attachment #1.1: Type: text/plain, Size: 1073 bytes --]
On Tue, 2017-11-07 at 10:30 +0530, Vinod Koul wrote:
> Hi,
>
> Please PULL to receive update for GLK audio firmware.
>
> The following changes since commit bf04291309d3169c0ad3b8db52564235bbd08e30:
>
> WHENCE: Add new qed firmware (2017-10-09 18:03:26 +0100)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/firmware.git glk
>
> for you to fetch changes up to b964279f2d9955a6ce00d3a672b273ae4d7a362f:
>
> linux-firmware: intel: Update Geminilake audio firmware (2017-11-07 10:25:50 +0530)
>
> ----------------------------------------------------------------
> Pradeep Tewani (1):
> linux-firmware: intel: Update Geminilake audio firmware
>
> WHENCE | 4 +++-
> intel/dsp_fw_glk.bin | 2 +-
> intel/dsp_fw_glk_v2880.bin | Bin 0 -> 505608 bytes
> 3 files changed, 4 insertions(+), 2 deletions(-)
> create mode 100644 intel/dsp_fw_glk_v2880.bin
Pulled, thanks.
Ben.
--
Ben Hutchings
When in doubt, use brute force. - Ken Thompson
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2017-11-23 1:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 5:00 [GIT PULL]: Geminilake audio firmware update Vinod Koul
2017-11-23 1:49 ` Ben Hutchings [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=1511401748.14687.14.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=linux-firmware@kernel.org \
--cc=patches.audio@intel.com \
--cc=vinod.koul@intel.com \
/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).