From: Javier Martinez Canillas <javier@osg.samsung.com>
To: Matthias Kaehlcke <mka@chromium.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Douglas Anderson <dianders@chromium.org>,
Brian Norris <briannorris@chromium.org>
Subject: Re: [PATCH v4] regulator: core: Limit propagation of parent voltage count and list
Date: Mon, 27 Mar 2017 20:02:57 -0400 [thread overview]
Message-ID: <06bc54e1-9c6a-3d4d-c509-33dfcb2b844d@osg.samsung.com> (raw)
In-Reply-To: <20170327235412.85058-1-mka@chromium.org>
Hello Matthias,
On 03/27/2017 07:54 PM, Matthias Kaehlcke wrote:
> Commit 26988efe11b1 ("regulator: core: Allow to get voltage count and
> list from parent") introduces the propagation of the parent voltage
> count and list for regulators that don't provide this information
> themselves. The goal is to support simple switch regulators, however as
> a side effect normal continuous regulators can leak details of their
> supplies and provide consumers with inconsistent information.
>
> Limit the propagation of the voltage count and list to switch
> regulators.
>
> Fixes: 26988efe11b1 ("regulator: core: Allow to get voltage count and
> list from parent")
> Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
You should had carried collected tags since this version is almost
identical to the previous one, but for reference here are again:
Reviewed-by: Javier Martinez Canillas <javier@osg.samsung.com>
Tested-by: Javier Martinez Canillas <javier@osg.samsung.com>
Best regards,
--
Javier Martinez Canillas
Open Source Group
Samsung Research America
next prev parent reply other threads:[~2017-03-28 0:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 23:54 Matthias Kaehlcke
2017-03-28 0:02 ` Javier Martinez Canillas [this message]
2017-03-29 11:54 ` Applied "regulator: core: Limit propagation of parent voltage count and list" to the regulator tree 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=06bc54e1-9c6a-3d4d-c509-33dfcb2b844d@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=briannorris@chromium.org \
--cc=broonie@kernel.org \
--cc=dianders@chromium.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.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
all inboxes | Powered by JetHome®