From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: Randy Dunlap <randy.dunlap@oracle.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: Sat, 21 May 2011 12:51:03 +0100 [thread overview]
Message-ID: <1305978663.3317.7.camel@odin> (raw)
In-Reply-To: <20110518194311.GB5077@opensource.wolfsonmicro.com>
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>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
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
next prev parent reply other threads:[~2011-05-21 11:51 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 [this message]
2011-05-26 16:05 ` Randy Dunlap
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=1305978663.3317.7.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=haojian.zhuang@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sameo@linux.intel.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.