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
| ||
|
Date: Tue, 7 Aug 2012 10:09:09 +0800 From: Shawn Guo <shawn.guo@...aro.org> To: Matt Sealey <matt@...esi-usa.com> CC: Robert Schwebel <r.schwebel@...gutronix.de>, Mark Brown <broonie@...nsource.wolfsonmicro.com>, Anton Vorontsov <anton.vorontsov@...aro.org>, Russell King <linux@....linux.org.uk>, John Stultz <john.stultz@...aro.org>, <linux-kernel@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>, <linaro-kernel@...ts.linaro.org>, Sascha Hauer <kernel@...gutronix.de> Subject: Re: [PATCH 4/9] ASoC: imx: Don't use {en,dis}able_fiq() calls On Mon, Aug 06, 2012 at 03:39:50PM -0500, Matt Sealey wrote: > * make sure there's no weird FIQ stuff floating around that has so far > relied on SND_SOC_IMX_PCM_FIQ doing select FIQ before I make it not Acked on changing SND_IMX_SOC to SND_SOC_IMX_PCM_FIQ in arch/arm/plat-mxc/Makefile. > compile in for other boards (since otherwise no i.MX processor selects > FIQ if they're not using that driver, it could be simply coincidence > nobody noticed). I don't want to be the one submitting a patch I can't > test which mysteriously breaks every MX28 on the planet (since Rob, > Shawn, Sascha might be the ones swearing at me instead) > Though i.MX23 and i.MX28 are named in i.MX family, they are actually a different architecture from IMX/MXC. It's MXS, nothing to do with SSI. Folder sound/soc/mxs/ is the one for i.MX28. -- Regards, Shawn -- 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