alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Kyle McMartin <kyle@infradead.org>
To: Vinod Koul <vinod.koul@intel.com>
Cc: Patches Audio <patches.audio@intel.com>,
	alsa-devel@alsa-project.org, linux-firmware@kernel.org
Subject: Re: [GIT PULL] Gemini lake audio firmware
Date: Fri, 3 Mar 2017 09:52:07 -0800	[thread overview]
Message-ID: <20170303175207.GZ13400@bombadil.infradead.org> (raw)
In-Reply-To: <20170303133525.GT2843@localhost>

On Fri, Mar 03, 2017 at 07:05:25PM +0530, Vinod Koul wrote:
> Hi,
> 
> Please pull to receive the Geminilake audio firmware used in Intel Geminilake
> devices with Audio DSP.
> 
> The following changes since commit 4b9559fb0565f582a21a4070a81a3b6a7d77610b:
> 
>   linux-firmware: update firmware file for atusb (2016-12-07 01:01:04 +0000)
> 
> 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 dc76591484e43cc031a28eeecae68196a98a1550:
> 
>   linux-firmware: intel: Add Geminilake audio firmware (2017-03-03 15:40:35 +0530)
> 

Pulled, thanks Vinod.

regards, Kyle

> ----------------------------------------------------------------
> Subhransu S. Prusty (1):
>       linux-firmware: intel: Add Geminilake audio firmware
> 
>  WHENCE                     |   6 ++++++
>  intel/dsp_fw_glk.bin       |   1 +
>  intel/dsp_fw_glk_v1814.bin | Bin 0 -> 505608 bytes
>  3 files changed, 7 insertions(+)
>  create mode 120000 intel/dsp_fw_glk.bin
>  create mode 100644 intel/dsp_fw_glk_v1814.bin
> 
> Thanks
> -- 
> ~Vinod

      reply	other threads:[~2017-03-03 17:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03 13:35 [GIT PULL] Gemini lake audio firmware Vinod Koul
2017-03-03 17:52 ` Kyle McMartin [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=20170303175207.GZ13400@bombadil.infradead.org \
    --to=kyle@infradead.org \
    --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).