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: Wed, 18 Nov 2015 10:53:23 +0900 From: Krzysztof Kozlowski <k.kozlowski@...sung.com> To: Arnd Bergmann <arnd@...db.de>, Mark Brown <broonie@...nel.org> Cc: alsa-devel@...a-project.org, linux-samsung-soc@...r.kernel.org, Heiko Stuebner <heiko@...ech.de>, Sangbeom Kim <sbkim73@...sung.com>, Liam Girdwood <lgirdwood@...il.com>, linux-kernel@...r.kernel.org, Vinod Koul <vinod.koul@...el.com>, Kukjin Kim <kgene@...nel.org>, linux-arm-kernel@...ts.infradead.org Subject: Re: [PATCHv2 2/3] ASoC: s3c24xx-i2s: pass DMA channels as platform data On 18.11.2015 00:54, Arnd Bergmann wrote: > This is a minor cleanup to make the s3c2412-i2s and s3c24xx-i2s > drivers independent of the mach/dma.h header file and to allow > removing the dependency on the specific dmaengine driver in the > next patch. > > As a side not, only the s3c24xx-i2s driver seems to still be > used, while the definition of the s3c2412-i2s platform device was > removed in commit 6d259a25b56d ("ARM: SAMSUNG: use static > declaration when it is not used in other files") after it had > never been referenced since its introduction in f0fba2ad1b6b > ("ASoC: multi-component - ASoC Multi-Component Support"). > > Apparently it should have been used by mach-jive.c, but that > never happened. My patch at this point leaves the current state > unchanged, we can decide whether to fix or delete the jive > driver and s3c2412-i2s another time. > > Signed-off-by: Arnd Bergmann <arnd@...db.de> > --- > v2: check for NULL pdata > Reviewed-by: Krzysztof Kozlowski <k.kozlowski@...sung.com> Best regards, Krzysztof -- 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