public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: broonie@opensource.wolfsonmicro.com
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
	sameo@linux.intel.com, lrg@ti.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] regulator: tps6586x: register regulator even if no init data
Date: Tue, 04 Sep 2012 14:47:31 -0600	[thread overview]
Message-ID: <504668E3.1060907@wwwdotorg.org> (raw)
In-Reply-To: <1346252473-30068-1-git-send-email-ldewangan@nvidia.com>

On 08/29/2012 09:01 AM, Laxman Dewangan wrote:
> Register all TPS6586x regulators even if there is no regulator
> init data for platform i.e. without any user-supplied constraints.
> 
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>

Tested-by: Stephen Warren <swarren@nvidia.com>

Note that this patch depends on the patch I just posted titled
"regulator: tps6586x: add support for SYS rail". I also believe Laxman
will be posting another patch based on these 2 soon (it will move the
regulator DT parsing out of the MFD driver into the regulator driver),
so I guess it makes sense to take them all through the same TPS6586x
topic branch in the regulator tree.

That all said, I only care about merging the first patch, "regulator:
tps6586x: add support for SYS rail", into the Tegra tree, so please
don't wait for the 3rd patch before making any tag for me to pull.

Thanks.

  parent reply	other threads:[~2012-09-04 20:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-29 15:01 [PATCH V2] regulator: tps6586x: register regulator even if no init data Laxman Dewangan
2012-08-29 17:38 ` Stephen Warren
2012-09-04 20:47 ` Stephen Warren [this message]
2012-09-05  8:02   ` Laxman Dewangan
2012-09-05 15:33     ` Stephen Warren
2012-09-06 11:31       ` 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=504668E3.1060907@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=ldewangan@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=sameo@linux.intel.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