LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: manjunatha_halli@ti.com
Cc: mchehab@infradead.org, hverkuil@xs4all.nl,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Subject: [PATCH -next] drivers:media:radio: wl128x: fix printk format and text
Date: Fri, 18 Mar 2011 09:18:54 -0700 [thread overview]
Message-ID: <20110318091854.b234ad3e.randy.dunlap@oracle.com> (raw)
In-Reply-To: <1294745487-29138-4-git-send-email-manjunatha_halli@ti.com>
What happened to this driver in linux-next of 2011.0318?
It's in linux-next of 2011.0317.
Here's a patch that was prepared against linux-next of 2011.0317.
---
From: Randy Dunlap <randy.dunlap@oracle.com>
Fix text spacing and grammar.
Fix printk format warning:
drivers/media/radio/wl128x/fmdrv_common.c:274: warning: format '%d' expects type 'int', but argument 4 has type 'long unsigned int'
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
drivers/media/radio/wl128x/fmdrv_common.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- linux-next-20110317.orig/drivers/media/radio/wl128x/fmdrv_common.c
+++ linux-next-20110317/drivers/media/radio/wl128x/fmdrv_common.c
@@ -271,8 +271,8 @@ static void recv_tasklet(unsigned long a
/* Process all packets in the RX queue */
while ((skb = skb_dequeue(&fmdev->rx_q))) {
if (skb->len < sizeof(struct fm_event_msg_hdr)) {
- fmerr("skb(%p) has only %d bytes"
- "atleast need %d bytes to decode\n", skb,
+ fmerr("skb(%p) has only %d bytes; "
+ "need at least %zd bytes to decode\n", skb,
skb->len, sizeof(struct fm_event_msg_hdr));
kfree_skb(skb);
continue;
next prev parent reply other threads:[~2011-03-18 16:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 11:31 [RFC V10 0/7] FM V4L2 drivers for WL128x manjunatha_halli
2011-01-11 11:31 ` [RFC V10 1/7] drivers:media:radio: wl128x: FM Driver common header file manjunatha_halli
2011-01-11 11:17 ` Felipe Balbi
2011-01-11 11:31 ` [RFC V10 2/7] drivers:media:radio: wl128x: FM Driver V4L2 sources manjunatha_halli
2011-01-11 11:21 ` Felipe Balbi
2011-01-11 11:31 ` [RFC V10 3/7] drivers:media:radio: wl128x: FM Driver Common sources manjunatha_halli
2011-01-11 11:24 ` Felipe Balbi
2011-01-11 12:16 ` halli manjunatha
2011-01-11 12:42 ` Raja Mani
2011-01-17 10:15 ` halli manjunatha
2011-01-17 10:33 ` Hans Verkuil
2011-01-18 13:19 ` halli manjunatha
2011-01-19 19:12 ` Mauro Carvalho Chehab
2011-01-20 9:39 ` halli manjunatha
2011-01-11 11:31 ` [RFC V10 4/7] drivers:media:radio: wl128x: FM driver RX sources manjunatha_halli
2011-01-11 11:31 ` [RFC V10 5/7] drivers:media:radio: wl128x: FM driver TX sources manjunatha_halli
2011-01-11 11:31 ` [RFC V10 6/7] drivers:media:radio: wl128x: Kconfig & Makefile for wl128x driver manjunatha_halli
2011-01-11 11:30 ` Felipe Balbi
2011-01-11 11:31 ` [RFC V10 7/7] drivers:media:radio: Update Kconfig and Makefile for wl128x FM driver manjunatha_halli
2011-03-18 16:18 ` Randy Dunlap [this message]
2011-03-22 18:23 ` [PATCH -next] drivers:media:radio: wl128x: fix printk format and text Mauro Carvalho Chehab
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=20110318091854.b234ad3e.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=manjunatha_halli@ti.com \
--cc=mchehab@infradead.org \
--subject='Re: [PATCH -next] drivers:media:radio: wl128x: fix printk format and text' \
/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
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).