| 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, 1 Apr 2014 21:21:57 +0800 From: Nicolin Chen <Guangyu.Chen@...escale.com> To: Mark Brown <broonie@...nel.org> CC: <linux-kernel@...r.kernel.org>, <linuxppc-dev@...ts.ozlabs.org>, <alsa-devel@...a-project.org>, <timur@...i.org>, <Li.Xiubo@...escale.com> Subject: Re: [PATCH bisect 2/2] ASoC: fsl_sai: Separately enable interrupts for Tx and Rx streams On Tue, Apr 01, 2014 at 01:07:15PM +0100, Mark Brown wrote: > On Tue, Apr 01, 2014 at 11:17:07AM +0800, Nicolin Chen wrote: > > We only enable one side interrupt for each stream since over/underrun > > on the opposite stream would be resulted from what we previously did, > > enabling TERE but remaining FRDE disabled, even though the xrun on the > > opposite direction will not break the current stream. > > This still doesn't apply against fsl-sai (nor for-next). Sir, I just rebased my for-next branch again and found that it's missing two applied patches: "ASoC: fsl_sai: Add isr to deal with error flag" and "ASoC: fsl_sai: Improve fsl_sai_isr()", so that's why this PATCH-2 could not be applied against it as it needs the macro that's included in the patch "ASoC: fsl_sai: Add isr to deal with error flag". What should I do now? Thank you, Nicolin -- 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