From: Greg KH <greg@kroah.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>
Subject: Re: linux-next: Tree for October 30
Date: Thu, 30 Oct 2008 23:25:57 -0700 [thread overview]
Message-ID: <20081031062557.GB22015@kroah.com> (raw)
In-Reply-To: <20081030165532.802375f8.randy.dunlap@oracle.com>
On Thu, Oct 30, 2008 at 04:55:32PM -0700, Randy Dunlap wrote:
> On Thu, 30 Oct 2008 17:30:30 +1100 Stephen Rothwell wrote:
>
>
> Greg told me that he would fix these, but they are still around:
>
> drivers/staging/poch/poch.c:388: warning: format '%x' expects type 'unsigned int', but argument 4 has type 'dma_addr_t'
>
> drivers/usb/misc/vstusb.c:623: warning: format '%d' expects type 'int', but argument 5 has type 'size_t'
Hm, sorry about that, I thought I did :(
I'll work on it in the morning.
thanks,
greg k-h
next prev parent reply other threads:[~2008-10-31 6:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 6:30 linux-next: Tree for October 30 Stephen Rothwell
2008-10-30 18:03 ` next-20081030: voyager compile busted Alexey Dobriyan
2008-10-30 20:24 ` James Bottomley
2008-10-30 20:52 ` Ingo Molnar
2008-10-30 20:58 ` James Bottomley
2008-10-30 21:07 ` Ingo Molnar
2008-10-30 21:21 ` James Bottomley
2008-10-30 21:42 ` H. Peter Anvin
2008-10-30 21:47 ` James Bottomley
2008-10-30 21:50 ` H. Peter Anvin
2008-10-30 22:40 ` Ingo Molnar
2008-10-31 17:42 ` James Bottomley
2008-10-30 21:24 ` Alexey Dobriyan
2008-10-30 23:42 ` Tony Breeds
2008-10-30 23:55 ` linux-next: Tree for October 30 Randy Dunlap
2008-10-31 6:25 ` Greg KH [this message]
2008-10-31 16:40 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2009-10-30 9:09 Stephen Rothwell
2009-10-30 15:30 ` Gregory Haskins
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=20081031062557.GB22015@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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.