From: Vinod Koul <vinod.koul@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: "Fang, Yang A" <yang.a.fang@intel.com>,
alsa-devel@alsa-project.org, subhransu.s.prusty@intel.com,
lgirdwood@gmail.com
Subject: Re: [PATCH 2/4] ASoC: Intel: use correct firmware name
Date: Mon, 3 Nov 2014 10:08:22 +0530 [thread overview]
Message-ID: <20141103043822.GK28745@intel.com> (raw)
In-Reply-To: <20141031125138.GX18557@sirena.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 489 bytes --]
On Fri, Oct 31, 2014 at 12:51:38PM +0000, Mark Brown wrote:
> On Thu, Oct 30, 2014 at 04:20:57PM +0530, Vinod Koul wrote:
> > From: Fang, Yang A <yang.a.fang@intel.com>
> >
> > The firmware name was used worngly, so fix it up
>
> Applied, thanks. I am wondering how the code was originally tested...
The firmware name was not right even in the binary thats how we never caught
this early on.
Thanks for applying all the patches, I will updated the ACPI stuff
--
~Vinod
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2014-11-03 5:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 10:50 [PATCH 0/4] ASoC: Intel: add compressed support Vinod Koul
2014-10-30 10:50 ` [PATCH 1/4] ASoC: Intel: sst: load firmware using async callback Vinod Koul
2014-10-31 12:51 ` Mark Brown
2014-10-30 10:50 ` [PATCH 2/4] ASoC: Intel: use correct firmware name Vinod Koul
2014-10-31 12:51 ` Mark Brown
2014-11-03 4:38 ` Vinod Koul [this message]
2014-10-30 10:50 ` [PATCH 3/4] ASoC: mfld-compress: implement .power callback Vinod Koul
2014-10-31 12:52 ` Mark Brown
2014-10-30 10:50 ` [PATCH 4/4] ASoC: Intel: sst - add compressed ops handling Vinod Koul
2014-10-31 12:52 ` Mark Brown
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=20141103043822.GK28745@intel.com \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=subhransu.s.prusty@intel.com \
--cc=yang.a.fang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.