lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150205184822.GE13647@H87M>
Date:	Thu, 5 Feb 2015 10:48:22 -0800
From:	Kevin Strasser <kevin.strasser@...ux.intel.com>
To:	Mark Brown <broonie@...nel.org>
Cc:	alsa-devel@...a-project.org, Vinod Koul <vinod.koul@...el.com>,
	Mengdong Lin <mengdong.lin@...el.com>,
	Liam Girdwood <lgirdwood@...il.com>,
	linux-kernel@...r.kernel.org, Yang Fang <yang.a.fang@...el.com>
Subject: Re: [alsa-devel] [PATCH] ASoC: Intel: fix sst firmware path

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ