linux-kernel - Re: [PATCH -next] sound/soc: fix printk format warning

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: <4CA228CE.9000707@oracle.com>
Date:	Tue, 28 Sep 2010 10:41:34 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
CC:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Liam Girdwood <lrg@...mlogic.co.uk>
Subject: Re: [PATCH -next] sound/soc: fix printk format warning

On 09/28/10 10:33, Mark Brown wrote:
> On Tue, Sep 28, 2010 at 09:58:46AM -0700, Randy Dunlap wrote:
>> From: Randy Dunlap <randy.dunlap@...cle.com>
> 
>> Fix dev_printk format warning:
> 
>> sound/soc/codecs/wm8985.c:731: warning: format '%d' expects type 'int', but argument 4 has type 'size_t'
> 
>> Signed-off-by: Randy Dunlap <randy.dunlap@...cle.com>
> 
> Takashi already fixed that (and the change already seems to be in
> -next...).

I don't see the fix in linux-next 2010-0928.
Aha, he changed the variable type.  OK, thanks.

> When reporting type based warnings please always report the
> architecture you're building for, GCC seems to only generate the
> warnings if there's a difference in the underlying typedef which means
> that they don't always trigger on every architecture.


-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
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/