linux-kernel - [PATCH -next] soc: fix printk format in soc-dapm.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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <4F8CC0E9.3010407@xenotime.net>
Date:	Mon, 16 Apr 2012 18:01:29 -0700
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
CC:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Liam Girdwood <lrg@...com>,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	alsa-devel@...a-project.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: [PATCH -next] soc: fix printk format in soc-dapm.c

From: Randy Dunlap <rdunlap@...otime.net>

Fix printk format warning for 'formats':

sound/soc/soc-dapm.c:2913:5: warning: format '%lx' expects type 'long unsigned int', but argument 3 has type 'u64'

Signed-off-by: Randy Dunlap <rdunlap@...otime.net>
Cc:	Liam Girdwood <lrg@...com>
Cc:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	alsa-devel@...a-project.org
---
 sound/soc/soc-dapm.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- linux-next-20120416.orig/sound/soc/soc-dapm.c
+++ linux-next-20120416/sound/soc/soc-dapm.c
@@ -2909,7 +2909,7 @@ static int snd_soc_dai_link_event(struct
 	if (config->formats) {
 		fmt = ffs(config->formats) - 1;
 	} else {
-		dev_warn(w->dapm->dev, "Invalid format %lx specified\n",
+		dev_warn(w->dapm->dev, "Invalid format %llx specified\n",
 			 config->formats);
 		fmt = 0;
 	}
--
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/