linux-kernel - breakage in linux-next sound/soc/blackfin/bf5xx-i2s.c

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 11 Dec 2008 11:02:24 -0500
From:	"Mike Frysinger" <vapier.adi@...il.com>
To:	broonie@...nsource.wolfsonmicro.com
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: breakage in linux-next sound/soc/blackfin/bf5xx-i2s.c

your recent change 3f4b783cfd (ASoC: Register platform DAIs) is
incorrect for sound/soc/blackfin/bf5xx-i2s.c.

the change made there:
+static int __devinit bfin_i2s_init(void)
+{
+       return snd_soc_register_dai(&bfin_i2s_dai);
+}
+module_init(bfin_i2s_init);
+
+static void __exit bfin_i2s_exit(void)
+{
+       snd_soc_unregister_dai(&bfin_i2s_dai);
+}
+module_exit(bfin_i2s_exit);

leads to this:
sound/soc/blackfin/bf5xx-i2s.c:294: warning: initialization from
incompatible pointer type
sound/soc/blackfin/bf5xx-i2s.c: In function 'bfin_i2s_init':
sound/soc/blackfin/bf5xx-i2s.c:318: error: 'bfin_i2s_dai' undeclared
(first use in this function)
sound/soc/blackfin/bf5xx-i2s.c:318: error: (Each undeclared identifier
is reported only once
sound/soc/blackfin/bf5xx-i2s.c:318: error: for each function it appears in.)
sound/soc/blackfin/bf5xx-i2s.c: In function 'bfin_i2s_exit':
sound/soc/blackfin/bf5xx-i2s.c:324: error: 'bfin_i2s_dai' undeclared
(first use in this function)
make[3]: *** [sound/soc/blackfin/bf5xx-i2s.o] Error 1
make[2]: *** [sound/soc/blackfin] Error 2
make[1]: *** [sound/soc] Error 2
make: *** [sound] Error 2

since the variable is named "bf5xx_i2s_dai", not "bfin_i2s_dai"
-mike
--
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/