From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] regulator: Use _regulator_get_voltage() consistently
Date: Fri, 10 Dec 2010 22:13:47 +0000 [thread overview]
Message-ID: <1292019227.3422.14.camel@odin> (raw)
In-Reply-To: <1292002088-9644-1-git-send-email-broonie@opensource.wolfsonmicro.com>
On Fri, 2010-12-10 at 17:28 +0000, Mark Brown wrote:
> Rather than referencing the get_voltage() operation directly in the
> ops struct use the internal _regulator_get_voltage() API call to do
> so, facilitating refactoring.
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
All Applied.
Thanks
Liam
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
prev parent reply other threads:[~2010-12-10 22:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 17:28 [PATCH 1/3] regulator: Use _regulator_get_voltage() consistently Mark Brown
2010-12-10 17:28 ` [PATCH 2/3] regulator: Allow drivers to report voltages as selectors Mark Brown
2010-12-10 17:28 ` [PATCH 3/3] regulator: Convert WM831x drivers to use get_voltage_sel() Mark Brown
2010-12-10 22:13 ` Liam Girdwood [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=1292019227.3422.14.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox