From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: linux-kernel@vger.kernel.org, Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] regulator: arizona-micsupp: Fix choosing selector in arizona_micsupp_map_voltage
Date: Tue, 26 Jun 2012 11:48:24 +0100 [thread overview]
Message-ID: <20120626104823.GP30406@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1340707078.3075.1.camel@phoenix>
[-- Attachment #1: Type: text/plain, Size: 159 bytes --]
On Tue, Jun 26, 2012 at 06:37:58PM +0800, Axel Lin wrote:
> If min_uV is in the range of: 3250001~3269999,
> current code uses the equation:
Applied, thanks.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-06-26 10:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 10:37 [PATCH] regulator: arizona-micsupp: Fix choosing selector in arizona_micsupp_map_voltage Axel Lin
2012-06-26 10:48 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-06-26 8:01 Axel Lin
2012-06-26 9:08 ` Mark Brown
2012-06-26 9:27 ` Axel Lin
2012-06-26 9:52 ` Mark Brown
2012-06-26 10:32 ` Axel Lin
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=20120626104823.GP30406@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=axel.lin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).