linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, gregkh@suse.de
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	devel@driverdev.osuosl.org
Subject: [PATCH -next] staging/line6: fix printk formats
Date: Thu, 12 Nov 2009 15:46:01 -0800	[thread overview]
Message-ID: <20091112154601.97a4e2ab.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20091112195101.63263490.sfr@canb.auug.org.au>

From: Randy Dunlap <randy.dunlap@oracle.com>

Fix printk format warnings in line6/pod.c; sizeof() is of type
size_t, so use %zu.

drivers/staging/line6/pod.c:581: warning: format '%d' expects type 'int', but argument 4 has type 'long unsigned int'
drivers/staging/line6/pod.c:693: warning: format '%d' expects type 'int', but argument 4 has type 'long unsigned int'

Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
 drivers/staging/line6/pod.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

--- linux-next-20091112.orig/drivers/staging/line6/pod.c
+++ linux-next-20091112/drivers/staging/line6/pod.c
@@ -579,7 +579,7 @@ static ssize_t pod_set_dump(struct devic
 
 	if (count != sizeof(pod->prog_data)) {
 		dev_err(pod->line6.ifcdev,
-			"data block must be exactly %d bytes\n",
+			"data block must be exactly %zu bytes\n",
 			sizeof(pod->prog_data));
 		return -EINVAL;
 	}
@@ -691,7 +691,7 @@ static ssize_t pod_set_dump_buf(struct d
 
 	if (count != sizeof(pod->prog_data)) {
 		dev_err(pod->line6.ifcdev,
-						"data block must be exactly %d bytes\n",
+						"data block must be exactly %zu bytes\n",
 						sizeof(pod->prog_data));
 		return -EINVAL;
 	}

      parent reply	other threads:[~2009-11-12 23:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-12  8:51 linux-next: Tree for November 12 Stephen Rothwell
2009-11-12 11:53 ` -next: Nov 12 - kernel BUG at kernel/sched.c:7359! Sachin Sant
2009-11-12 12:10   ` Peter Zijlstra
2009-11-12 12:23     ` Sachin Sant
2009-11-12 12:27       ` Peter Zijlstra
2009-11-12 17:10         ` Peter Zijlstra
2009-11-13  9:00           ` Sachin Sant
2009-11-13  9:06             ` Peter Zijlstra
2009-11-13  9:58           ` Gautham R Shenoy
2009-11-13 10:16             ` Peter Zijlstra
2009-11-13 10:31               ` Peter Zijlstra
2009-11-13 10:49                 ` Peter Zijlstra
2009-11-13 11:44                 ` Sachin Sant
2009-11-13 16:12                 ` Mike Galbraith
2009-11-23  9:53                 ` Sachin Sant
2009-11-25 13:42                   ` Peter Zijlstra
2009-11-26  4:39                     ` Sachin Sant
2009-12-04 12:06                     ` Sachin Sant
2009-12-04 12:16                       ` Peter Zijlstra
2009-12-07  6:16                         ` Sachin Sant
2009-12-12  7:09                     ` Max Krasnyansky
2009-11-12 17:40 ` linux-next: Tree for November 12 (acpi/processor.h) Randy Dunlap
2009-11-12 18:09   ` linux-next: Tree for November 12 (acpi_processor_get_bios_limit) Randy Dunlap
2009-11-12 23:46 ` Randy Dunlap [this message]

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=20091112154601.97a4e2ab.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).