From: Joe Perches <joe@perches.com>
To: Liam Girdwood <lrg@slimlogic.co.uk>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Daniel Walker <dwalker@codeaurora.org>,
linux-kernel@vger.kernel.org, bleong@codeaurora.org
Subject: Re: [PATCH 1/2] drivers: regulator: core: use pr_fmt
Date: Fri, 19 Nov 2010 09:07:09 -0800 [thread overview]
Message-ID: <1290186429.28541.3.camel@Joe-Laptop> (raw)
In-Reply-To: <1290164963.3276.2.camel@odin>
On Fri, 2010-11-19 at 11:09 +0000, Liam Girdwood wrote:
> On Thu, 2010-11-18 at 10:35 +0000, Mark Brown wrote:
> > On Wed, Nov 17, 2010 at 03:30:27PM -0800, Daniel Walker wrote:
> > > This adds a pr_fmt line which uses the __func__ macro. I also
> > > convert the current pr_ lines to remove their __func__ usage.
> > > Cc: bleong@codeaurora.org
> > > Signed-off-by: Daniel Walker <dwalker@codeaurora.org>
> > Both patches
> > Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> Applied with some merge fixups.
> Joe, I'd be happy to take any subsequent patches you have for this.
After these patches show up in -next.
I think there were some other patches about
as well, so maybe in a week or so.
prev parent reply other threads:[~2010-11-19 17:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 23:30 [PATCH 1/2] drivers: regulator: core: use pr_fmt Daniel Walker
2010-11-17 23:30 ` [PATCH 2/2] drivers: regulator: core: convert to using pr_ macros Daniel Walker
2010-11-18 0:36 ` Joe Perches
2010-11-18 1:30 ` Joe Perches
2010-11-18 13:30 ` Mark Brown
2010-11-18 13:29 ` Mark Brown
2010-11-18 16:29 ` Joe Perches
2010-11-18 0:29 ` [PATCH 1/2] drivers: regulator: core: use pr_fmt Joe Perches
2010-11-18 0:35 ` Daniel Walker
2010-11-18 10:37 ` Mark Brown
2010-11-18 16:44 ` Joe Perches
2010-11-18 10:35 ` Mark Brown
2010-11-19 11:09 ` Liam Girdwood
2010-11-19 17:07 ` Joe Perches [this message]
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=1290186429.28541.3.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=bleong@codeaurora.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dwalker@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
/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.