linux-kernel - Re: [PATCH] ASoC: Fix codec device id format used by some dai

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: <4D3B6F5A.2020309@metafoo.de>
Date:	Sun, 23 Jan 2011 00:59:22 +0100
From:	Lars-Peter Clausen <lars@...afoo.de>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
CC:	Liam Girdwood <lrg@...mlogic.co.uk>, alsa-devel@...a-project.org,
	linux-kernel@...r.kernel.org, "for 2.6.37" <stable@...nel.org>
Subject: Re: [PATCH] ASoC: Fix codec device id format used by some dai_links

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi

On 01/23/2011 12:33 AM, Mark Brown wrote:
> > On Sat, Jan 22, 2011 at 11:38:07PM +0100, Lars-Peter Clausen wrote:
> >
>> >>  sound/soc/imx/wm1133-ev1.c                     |    2 +-
Ok. I simply assumed that all of them were I2C devices since platform and SPI devices
use a completely different naming scheme.

I just went through the whole list and the wm8994 codec is a platform driver as well.
And on the jive board the wm8750 is connected through SPI.

> >
> > This at least is definitely wrong, the WM835x CODEC here is registered
> > as a platform device.  Please also check current kernels, a bunch of
> > these are already fixed.
The patch is based on your for-next branch.

- - Lars
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk07b1oACgkQBX4mSR26RiN3rQCeKvFG0eyVdxPh68vy3pasiKcv
iUUAn3lSz8cvKA95QI4Y9iRnyVk/bbWg
=0HnX
-----END PGP SIGNATURE-----
--
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/