From: Mark Brown <broonie@kernel.org>
To: Axel Lin <axel.lin@ingics.com>
Cc: "Joseph(Yossi) Hanin" <yhanin@marvell.com>,
Yi Zhang <yizhang@marvell.com>, Chao Xie <chao.xie@marvell.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator: 88pm800: Add missing n_voltages setting for bucks
Date: Fri, 19 Jul 2013 18:24:29 +0100 [thread overview]
Message-ID: <20130719172429.GP9858@sirena.org.uk> (raw)
In-Reply-To: <1374210382.895.2.camel@phoenix>
[-- Attachment #1: Type: text/plain, Size: 287 bytes --]
On Fri, Jul 19, 2013 at 01:06:22PM +0800, Axel Lin wrote:
> Some regulator APIs are broken if n_voltages setting is not set.
> e.g. regulator_count_voltages(), regulator_list_voltage(), and
> regulator_can_change_voltage() do not work if n_voltages setting is missing.
Applied, thanks.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-07-19 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 5:06 [PATCH] regulator: 88pm800: Add missing n_voltages setting for bucks Axel Lin
2013-07-19 17:24 ` Mark Brown [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=20130719172429.GP9858@sirena.org.uk \
--to=broonie@kernel.org \
--cc=axel.lin@ingics.com \
--cc=chao.xie@marvell.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yhanin@marvell.com \
--cc=yizhang@marvell.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