[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120619104254.GD3974@opensource.wolfsonmicro.com>
Date: Tue, 19 Jun 2012 11:43:18 +0100
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Laxman Dewangan <ldewangan@...dia.com>
Cc: "lrg@...com" <lrg@...com>,
"rob.herring@...xeda.com" <rob.herring@...xeda.com>,
"grant.likely@...retlab.ca" <grant.likely@...retlab.ca>,
"swarren@...dotorg.org" <swarren@...dotorg.org>,
"sameo@...ux.intel.com" <sameo@...ux.intel.com>,
"devicetree-discuss@...ts.ozlabs.org"
<devicetree-discuss@...ts.ozlabs.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] regulator: support for regulator match by
regulator-compatible
On Tue, Jun 19, 2012 at 03:04:00PM +0530, Laxman Dewangan wrote:
> Agree. Currently following regulators are using this (based on grep)
> mfd/tps6586x.c
> regulator/ab8500.c
> regulator/db8500-prcmu.c
> and regulator/tps65910.
That looks about right.
> If the related change in tps65910 is fine and there is no more
> concern/feedback on the approach then I can create a series of patch
> to modify the other regulator and related dts file to follow the
> same.
> If you want, I can make the new changes as part of this series or
> can start with new series.
> I like to go with new series patch for other change once this is accepted.
I've no concerns with the interface or the code itself other than the
usability issue with partial deployment so if you could do the updates
for the other drivers that'd be great. I'll hold off on applying this
until we've got everything else updated.
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists