From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH -next] sound/soc: fix printk format warning
Date: Tue, 28 Sep 2010 10:33:04 -0700 [thread overview]
Message-ID: <20100928173303.GD10739@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20100928095846.9d4c7641.randy.dunlap@oracle.com>
On Tue, Sep 28, 2010 at 09:58:46AM -0700, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.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@oracle.com>
Takashi already fixed that (and the change already seems to be in
-next...).
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.
next prev parent reply other threads:[~2010-09-28 17:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 4:18 linux-next: Tree for September 28 Stephen Rothwell
2010-09-28 16:48 ` [PATCH -next] hwmon/pkgtemp: fix build error Randy Dunlap
2010-09-28 16:53 ` [PATCH -next] ceph: fix debugfs warnings Randy Dunlap
2010-09-28 19:42 ` Sage Weil
2010-09-28 16:54 ` [PATCH -next] fs.h: fix functions for FILE_LOCKING disabled Randy Dunlap
2010-09-28 16:56 ` [PATCH -next] pch_gbe: add header files Randy Dunlap
2010-09-28 16:56 ` Randy Dunlap
2010-09-28 17:34 ` David Miller
2010-09-28 16:58 ` [PATCH -next] sound/soc: fix printk format warning Randy Dunlap
2010-09-28 17:33 ` Mark Brown [this message]
2010-09-28 17:41 ` Randy Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100928173303.GD10739@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.