From: Stephen Warren <swarren@wwwdotorg.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: broonie@opensource.wolfsonmicro.com, lrg@ti.com,
rob.herring@calxeda.com, grant.likely@secretlab.ca,
arnd@arndb.de, linus.walleij@linaro.org, lee.jones@linaro.org,
devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 1/3] ARM: dts: db8500: add property "regulator-compatible" regulator node
Date: Wed, 20 Jun 2012 12:48:41 -0600 [thread overview]
Message-ID: <4FE21B09.5000901@wwwdotorg.org> (raw)
In-Reply-To: <1340194987-23654-2-git-send-email-ldewangan@nvidia.com>
On 06/20/2012 06:23 AM, Laxman Dewangan wrote:
> Device's regulator matches their hardware counterparts with the
> property "regulator-compatible" of each child regulator node in
> place of the child node name.
> Add the property "regulator-compatible" for each regulator with
> their hardware counterpart's name.
>
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
This change is correct as far as it goes, so:
Acked-by: Stephen Warren <swarren@wwwdotorg.org>
That said, the DT still should be modified to match the rules of correct
DT formatting. That was a pre-existing issue though, so it's OK if that
doesn't happen in this patch, and I'm happy leaving that to the
maintainers of this file.
next prev parent reply other threads:[~2012-06-20 18:48 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 12:23 [PATCH V3 0/3] regulator: dt: add policy to match regulator with prop "regulator-compatible" Laxman Dewangan
2012-06-20 12:23 ` Laxman Dewangan
2012-06-20 12:23 ` [PATCH V3 1/3] ARM: dts: db8500: add property "regulator-compatible" regulator node Laxman Dewangan
2012-06-20 12:23 ` Laxman Dewangan
2012-06-20 18:48 ` Stephen Warren [this message]
2012-06-20 12:23 ` [PATCH V3 2/3] regulator: dt: regulator match by regulator-compatible Laxman Dewangan
2012-06-20 12:23 ` Laxman Dewangan
2012-06-20 19:24 ` Arnd Bergmann
2012-06-20 19:46 ` Mark Brown
2012-06-20 19:51 ` Stephen Warren
2012-06-20 23:37 ` Mark Brown
2012-06-20 20:40 ` Arnd Bergmann
2012-06-20 21:01 ` Stephen Warren
2012-06-20 23:35 ` Mark Brown
2012-06-21 14:50 ` Arnd Bergmann
2012-06-21 16:14 ` Mark Brown
2012-06-21 17:17 ` Arnd Bergmann
2012-06-21 17:31 ` Stephen Warren
2012-06-21 21:03 ` Arnd Bergmann
2012-06-21 22:52 ` Mark Brown
2012-06-21 19:45 ` Mark Brown
[not found] ` <20120621194544.GZ4037-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-06-21 21:53 ` Mitch Bradley
2012-06-21 22:36 ` Mark Brown
2012-06-20 23:15 ` Mark Brown
[not found] ` <20120620194609.GA4037-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-06-22 6:13 ` Thierry Reding
2012-06-22 6:13 ` Thierry Reding
2012-06-22 8:42 ` Mark Brown
2012-06-22 8:59 ` Thierry Reding
2012-06-22 9:12 ` Mark Brown
2012-06-26 9:02 ` Laxman Dewangan
2012-06-26 9:12 ` Mark Brown
2012-06-26 10:13 ` Lee Jones
2012-07-04 23:48 ` Linus Walleij
2012-07-05 7:16 ` Lee Jones
2012-06-20 12:23 ` [PATCH V3 3/3] regulator: dt: add policy to have property "regulator-compatible" Laxman Dewangan
2012-06-20 12:23 ` Laxman Dewangan
2012-06-20 18:52 ` Stephen Warren
2012-07-03 19:25 ` Mark Brown
2012-07-04 7:03 ` Laxman Dewangan
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=4FE21B09.5000901@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=arnd@arndb.de \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=ldewangan@nvidia.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=rob.herring@calxeda.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.