From: Randy Dunlap <randy.dunlap@oracle•com>
To: Liam Girdwood <lrg@slimlogic•co.uk>
Cc: Samuel Ortiz <sameo@linux•intel.com>,
Stephen Rothwell <sfr@canb•auug.org.au>,
Haojian Zhuang <haojian.zhuang@marvell•com>,
linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
Mark Brown <broonie@opensource•wolfsonmicro.com>
Subject: Re: [PATCH -next] regulator: fix 88pm8607.c printk format warning
Date: Thu, 26 May 2011 09:05:22 -0700 [thread overview]
Message-ID: <20110526090522.5d8c684b.randy.dunlap@oracle.com> (raw)
In-Reply-To: <1305978663.3317.7.camel@odin>
On Sat, 21 May 2011 12:51:03 +0100 Liam Girdwood wrote:
> On Wed, 2011-05-18 at 12:43 -0700, Mark Brown wrote:
> > On Wed, May 18, 2011 at 10:07:22AM -0700, Randy Dunlap wrote:
> > > From: Randy Dunlap <randy.dunlap@oracle•com>
> > >
> > > Fix printk format warning (seen on x86_64) and change to unsigned
> > > output format:
> > >
> > > drivers/regulator/88pm8607.c:417: warning: format '%d' expects type 'int', but argument 3 has type 'resource_size_t'
> >
> > Acked-by: Mark Brown <broonie@opensource•wolfsonmicro.com>
> > --
>
> Samuel, this doesn't apply against regulator-next. Iirc, the patches
> this is against went via mfd-next ? If, so any chance you could take
> this ?
>
> Thanks !
>
> Liam
Samuel,
Do you need this patch resent to you?
thanks,
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-05-26 16:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 4:54 linux-next: Tree for May 18 Stephen Rothwell
2011-05-18 17:07 ` [PATCH -next] regulator: fix 88pm8607.c printk format warning Randy Dunlap
2011-05-18 19:43 ` Mark Brown
2011-05-21 11:51 ` Liam Girdwood
2011-05-26 16:05 ` Randy Dunlap [this message]
2011-05-26 17:07 ` Samuel Ortiz
2011-05-26 17:16 ` Randy Dunlap
2011-05-26 18:00 ` Samuel Ortiz
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=20110526090522.5d8c684b.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle$(echo .)com \
--cc=broonie@opensource$(echo .)wolfsonmicro.com \
--cc=haojian.zhuang@marvell$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=lrg@slimlogic$(echo .)co.uk \
--cc=sameo@linux$(echo .)intel.com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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