From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] regulator: Clean up logging a bit
Date: Tue, 21 Dec 2010 14:47:08 +0000 [thread overview]
Message-ID: <1292942828.3296.45.camel@odin> (raw)
In-Reply-To: <1292601852-21905-1-git-send-email-broonie@opensource.wolfsonmicro.com>
On Fri, 2010-12-17 at 16:04 +0000, Mark Brown wrote:
> The recent introduction of standard regulator API logging macros means
> that all our log messages have at least the function name in them and
> logging that the constraints are for the regulator API is probably a
> bit much.
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Applied.
Thanks
Liam
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2010-12-21 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-17 16:04 [PATCH] regulator: Clean up logging a bit Mark Brown
2010-12-21 14:47 ` Liam Girdwood [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-12-17 16:05 Mark Brown
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=1292942828.3296.45.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=patches@opensource.wolfsonmicro.com \
/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.