From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
devel@driverdev.osuosl.org, Greg KH <gregkh@suse.de>
Subject: [PATCH -next] staging: fix wlan-ng printk format warning
Date: Thu, 25 Feb 2010 09:55:03 -0800 [thread overview]
Message-ID: <4B86B977.6040303@oracle.com> (raw)
In-Reply-To: <20100225183523.80361261.sfr@canb.auug.org.au>
From: Randy Dunlap <randy.dunlap@oracle.com>
Fix prism2fw.c printk format warning:
drivers/staging/wlan-ng/prism2fw.c:209: warning: format '%d' expects type 'int', but argument 3 has type 'size_t'
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
drivers/staging/wlan-ng/prism2fw.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-next-20100225.orig/drivers/staging/wlan-ng/prism2fw.c
+++ linux-next-20100225/drivers/staging/wlan-ng/prism2fw.c
@@ -205,7 +205,7 @@ int prism2_fwtry(struct usb_device *udev
return 1;
}
- printk(KERN_INFO "prism2_usb: %s will be processed, size %d\n",
+ printk(KERN_INFO "prism2_usb: %s will be processed, size %zu\n",
PRISM2_USB_FWFILE, fw_entry->size);
prism2_fwapply((const struct ihex_binrec *)fw_entry->data, wlandev);
next prev parent reply other threads:[~2010-02-25 18:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 7:35 linux-next: Tree for February 25 Stephen Rothwell
2010-02-25 17:21 ` linux-next: Tree for February 25 (quota) Randy Dunlap
2010-03-01 13:27 ` Jan Kara
2010-03-01 16:56 ` Randy Dunlap
2010-02-25 17:55 ` Randy Dunlap [this message]
2010-02-25 17:55 ` [PATCH -next] fs: fix compat_ioctl when CONFIG_BLOCK=n Randy Dunlap
2010-02-25 21:27 ` [PATCH -next] pktcdvd: improve BKL and compat_ioctl.c usage Arnd Bergmann
2010-02-25 22:10 ` Randy Dunlap
2010-03-02 12:06 ` Ingo Molnar
2010-03-02 23:38 ` Stephen Rothwell
2010-02-25 22:41 ` [PATCH -next] staging/pohmelfs: fix write_inode parameter warning Randy Dunlap
2010-02-26 0:41 ` Stephen Rothwell
2010-03-07 9:22 ` Geert Uytterhoeven
2010-03-07 15:50 ` Greg KH
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=4B86B977.6040303@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 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.