From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: "lrg@ti.com" <lrg@ti.com>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"swarren@wwwdotorg.org" <swarren@wwwdotorg.org>,
"sameo@linux.intel.com" <sameo@linux.intel.com>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] regulator: support for regulator match by regulator-compatible
Date: Tue, 19 Jun 2012 13:18:20 +0100 [thread overview]
Message-ID: <20120619121819.GN3974@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4FE06B31.3050306@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 665 bytes --]
On Tue, Jun 19, 2012 at 05:36:09PM +0530, Laxman Dewangan wrote:
> Just thinking on optimizing the changes require, we can do it in 3
> patches only:
> - In place of adding new api of_regulator_match_by_compatible(), we
> can modify the existing of_regulator_match() itself to look for
> regulator-compatible for matching. This can be done in first patch.
> - Need not to change the .c files, here just change the
> documentation of these regulator dt binding. All can be done in
> second patch.
> - Change the dts file to have this policy and seeing only on
> arm/boot/dts/db8500.dtsi for ab8500 and db8500-prcmu. So it will be
> third patch .
This seems fine.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-06-19 12:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 5:51 [PATCH 0/2] regulator: tps65910: dt: identify regulator by prop regulator-compatible Laxman Dewangan
2012-06-19 5:51 ` [PATCH 1/2] regulator: support for regulator match by regulator-compatible Laxman Dewangan
2012-06-19 9:32 ` Mark Brown
2012-06-19 9:34 ` Laxman Dewangan
2012-06-19 10:43 ` Mark Brown
2012-06-19 10:37 ` Laxman Dewangan
2012-06-19 12:06 ` Laxman Dewangan
2012-06-19 12:18 ` Mark Brown [this message]
2012-06-19 5:51 ` [PATCH 2/2] regulator: tps65910: dt: identify regulator " 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=20120619121819.GN3974@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=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=rob.herring@calxeda.com \
--cc=sameo@linux.intel.com \
--cc=swarren@wwwdotorg.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;
as well as URLs for NNTP newsgroup(s).