From: Vinod Koul <vinod.koul@intel.com>
To: Kevin Strasser <kevin.strasser@linux.intel.com>
Cc: Mark Brown <broonie@kernel.org>,
alsa-devel@alsa-project.org,
Mengdong Lin <mengdong.lin@intel.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org, Yang Fang <yang.a.fang@intel.com>
Subject: Re: [alsa-devel] [PATCH] ASoC: Intel: fix sst firmware path
Date: Thu, 5 Feb 2015 11:26:13 -0800 [thread overview]
Message-ID: <20150205192613.GA16547@intel.com> (raw)
In-Reply-To: <20150205184822.GE13647@H87M>
On Thu, Feb 05, 2015 at 10:48:22AM -0800, Kevin Strasser wrote:
> On Thu, Feb 05, 2015 at 06:14:58PM +0000, Mark Brown wrote:
> > On Wed, Feb 04, 2015 at 11:35:07AM -0800, Kevin Strasser wrote:
> > > All sst firmware is provided under the intel directory of the linux-firmware
> > > tree. By default this directory structure is kept when installing on a
> > > target system. Change the path to expect a default linux-firmware
> > > installation.
> >
> > Applied, thanks. It doesn't apply as a fix but that seems to be OK as the
> > only request_firmware() I spotted there appears to use intel/ prefixed
> > directories already.
>
> I'm a little confused. Do you want me to submit a version that can be applied as
> a fix? It seems to me that we want this patch in 3.19.
This patch wont apply as is, Mark requires you need to provide a patch
which can be applied against 3.19
--
~Vinod
next prev parent reply other threads:[~2015-02-05 19:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 19:35 [PATCH] ASoC: Intel: fix sst firmware path Kevin Strasser
2015-02-05 11:56 ` One Thousand Gnomes
2015-02-05 12:48 ` [alsa-devel] " Takashi Iwai
2015-02-05 14:37 ` Mark Brown
2015-02-05 18:14 ` Mark Brown
2015-02-05 18:48 ` Kevin Strasser
2015-02-05 18:48 ` [alsa-devel] " Kevin Strasser
2015-02-05 19:17 ` Mark Brown
2015-02-05 19:26 ` Vinod Koul [this message]
2015-02-05 20:12 ` [PATCH v2] ASoC: Intel: fix sst firmware path for cht-bsw-rt5672 Kevin Strasser
2015-02-05 20:16 ` 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=20150205192613.GA16547@intel.com \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kevin.strasser@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mengdong.lin@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.