From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: "grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
"lrg@ti.com" <lrg@ti.com>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH V2] regulator: dt: fix the name of regulator supply
Date: Sat, 19 May 2012 14:10:20 +0100 [thread overview]
Message-ID: <20120519131019.GS4039@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4FB79444.9010306@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 569 bytes --]
On Sat, May 19, 2012 at 06:08:28PM +0530, Laxman Dewangan wrote:
> The descriptor is set on the regulator driver and hence it need to
> be parse this in the regulator driver.
> We need to set the name regulator_desc->supply_name and hence it
> needs to be in dt binding documentation of that device/regulators.
> Is this what you recommend?
I'm sorry, I still can't understand what you're trying to say here
especially the first sentance. Listing the name of the supply in the
binding documentation doesn't seem like a bad idea if that's what you're
trying to say.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-05-19 13:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 19:34 [PATCH V2] regulator: dt: fix the name of regulator supply Laxman Dewangan
2012-05-19 10:43 ` Mark Brown
2012-05-19 12:38 ` Laxman Dewangan
2012-05-19 13:10 ` Mark Brown [this message]
2012-05-19 14:21 ` 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=20120519131019.GS4039@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=ldewangan@nvidia.com \
--cc=linux-doc@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 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).