All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: balbi@ti.com, Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	linux-usb <linux-usb@vger.kernel.org>,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] usb: fix renesas mod_gadget printk format warning
Date: Wed, 21 Dec 2011 13:24:13 -0800	[thread overview]
Message-ID: <20111221212413.GA16448@suse.de> (raw)
In-Reply-To: <4EF25B7D.8080905@xenotime.net>

On Wed, Dec 21, 2011 at 02:19:41PM -0800, Randy Dunlap wrote:
> On 12/21/2011 01:16 PM, Felipe Balbi wrote:
> > Hi,
> > 
> > On Wed, Dec 21, 2011 at 12:32:13PM -0800, Randy Dunlap wrote:
> >> From: Randy Dunlap <rdunlap@xenotime.net>
> >>
> >> Fix printk format warning:
> >>
> >> drivers/usb/renesas_usbhs/mod_gadget.c:188:3: warning: format '%x' expects type 'unsigned int', but argument 3 has type 'dma_addr_t'
> >>
> >> Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
> >> Cc: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> > 
> > a bit too late:
> > 
> > http://git.kernel.org/?p=linux/kernel/git/balbi/usb.git;a=commitdiff;h=8418153a4ccd38a3bc3229bc4bd161e3e5db88d2
> > 
> 
> OK, that's good.  But it's not in linux-next yet??

Give me a chance to catch up on stuff happening while I'm supposed to be
on vacation please...

  reply	other threads:[~2011-12-21 21:24 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-21  6:47 linux-next: Tree for Dec 21 Stephen Rothwell
2011-12-21 20:11 ` linux-next: Tree for Dec 21 (xen) Randy Dunlap
2011-12-21 19:30   ` Konrad Rzeszutek Wilk
2011-12-21 20:32 ` [PATCH] usb: fix renesas mod_gadget printk format warning Randy Dunlap
2011-12-21 21:16   ` Felipe Balbi
2011-12-21 22:19     ` Randy Dunlap
2011-12-21 21:24       ` Greg KH [this message]
2011-12-21 23:15 ` linux-next: Tree for Dec 21 Andrew Morton
2011-12-22 23:08   ` Andrew Morton
2011-12-22 23:20     ` Tejun Heo
2011-12-22 23:24       ` Andrew Morton
2011-12-22 23:38         ` Tejun Heo
2011-12-22 23:44           ` Andrew Morton
2011-12-22 23:46             ` Tejun Heo
2011-12-23  0:42               ` Tejun Heo
2011-12-24  5:13                 ` Hugh Dickins
2011-12-25  1:02                   ` [PATCH block/for-3.3/core] block: an exiting task should be allowed to create io_context Tejun Heo
2011-12-25 13:29                     ` Jens Axboe
2011-12-27 22:07                       ` Andrew Morton
2011-12-28  8:33                     ` Hugh Dickins
2011-12-28 16:48                       ` Tejun Heo
2011-12-28 17:50                         ` Hugh Dickins
2011-12-28 17:55                           ` Tejun Heo
2011-12-28 21:19                             ` Tejun Heo
2011-12-28 21:19                               ` Tejun Heo
2012-01-03 17:35                               ` Tejun Heo
2012-01-03 17:59                                 ` Tejun Heo
2012-01-03 20:09                                   ` Tejun Heo
2012-01-03 20:20                                     ` Jens Axboe
2012-01-03 22:13                                       ` Tejun Heo
2012-01-03 22:35                                         ` Tejun Heo
2012-01-05  1:24                                           ` Tejun Heo
2012-01-05 18:36                                             ` Hugh Dickins
2012-01-05 18:38                                               ` Tejun Heo
2012-01-06  2:17                                                 ` [PATCH block:for-3.3/core] cfq: merged request shouldn't jump to a different cfqq Tejun Heo
2012-01-06  2:36                                                   ` Tejun Heo
2012-01-06  3:14                                                     ` Shaohua Li
2012-01-06  3:04                                                       ` Tejun Heo
2012-01-06  3:30                                                         ` Tejun Heo
2012-01-06  3:52                                                           ` [PATCH block:for-3.3/core] block: disable ELEVATOR_INSERT_SORT_MERGE Tejun Heo
2012-01-06  4:19                                                             ` Shaohua Li
2012-01-06  4:38                                                               ` Tejun Heo
2012-01-06  8:15                                                                 ` Shaohua Li
2012-01-06 15:34                                                                   ` Tejun Heo
2012-01-06  3:34                                                         ` [PATCH block:for-3.3/core] cfq: merged request shouldn't jump to a different cfqq Shaohua Li
2012-01-06  3:22                                                           ` Tejun Heo
2012-01-06  4:15                                                             ` Shaohua Li
2012-01-06  4:40                                                               ` Tejun Heo
2012-01-06  2:47                                                   ` Shaohua Li
2011-12-25 16:08 ` linux-next: Tree for Dec 21 Sedat Dilek
2011-12-25 23:55   ` Stephen Rothwell

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=20111221212413.GA16448@suse.de \
    --to=gregkh@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=balbi@ti.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --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.