linux-kernel - Re: [alsa-devel] [PATCH] ASoC: Intel: fix sst firmware path

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: <s5h386kr0az.wl-tiwai@suse.de>
Date:	Thu, 05 Feb 2015 13:48:52 +0100
From:	Takashi Iwai <tiwai@...e.de>
To:	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
Cc:	Kevin Strasser <kevin.strasser@...ux.intel.com>,
	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>,
	Mark Brown <broonie@...nel.org>
Subject: Re: [alsa-devel] [PATCH] ASoC: Intel: fix sst firmware path

At Thu, 5 Feb 2015 11:56:06 +0000,
One Thousand Gnomes wrote:
> 
> On Wed,  4 Feb 2015 11:35:07 -0800
> Kevin Strasser <kevin.strasser@...ux.intel.com> 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.
> > 
> > Signed-off-by: Kevin Strasser <kevin.strasser@...ux.intel.com>
> 
> You just broken existing systems. I agree entirely with your change - but
> you need to search both paths for now and maybe in a few years time remove
> the old path.

IMO, it's fine in this case, as this stuff is new, merged first in
3.19.


thanks,

Takashi
--
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/