All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: ccross@android.com, olof@lixom.net, swarren@wwwdotorg.org,
	lrg@ti.com, thierry.reding@avionic-design.de,
	linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux-doc@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
	rob.herring@calxeda.com, grant.likely@secretlab.ca
Subject: Re: [PATCH 2/2] regulator: tps6586x: add support for input supply
Date: Fri, 13 Jul 2012 15:22:30 +0100	[thread overview]
Message-ID: <20120713142229.GM4215@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1342187432-18668-3-git-send-email-ldewangan@nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 293 bytes --]

On Fri, Jul 13, 2012 at 07:20:32PM +0530, Laxman Dewangan wrote:
> There is multiple voltage input pins on device which
> takes the voltage input for different voltage regulator.
> Support to configure the voltage input supplied by
> different regulator for each regulators.

Applied, thanks.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-07-13 14:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-13 13:50 [PATCH 0/2] regulator: tps6586x: support for input supply Laxman Dewangan
2012-07-13 13:50 ` Laxman Dewangan
     [not found] ` <1342187432-18668-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-07-13 13:50   ` [PATCH 1/2] ARM: tegra: harmony: add regulator supply name and its " Laxman Dewangan
2012-07-13 13:50     ` Laxman Dewangan
     [not found]     ` <1342187432-18668-2-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-07-23 20:49       ` Stephen Warren
2012-07-23 20:49         ` Stephen Warren
2012-07-13 13:50   ` [PATCH 2/2] regulator: tps6586x: add support for " Laxman Dewangan
2012-07-13 13:50     ` Laxman Dewangan
2012-07-13 14:22     ` Mark Brown [this message]
     [not found]       ` <20120713142229.GM4215-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-07-13 17:15         ` Laxman Dewangan
2012-07-13 17:15           ` Laxman Dewangan
2012-07-15 21:21           ` Mark Brown
     [not found]             ` <20120715212114.GI4041-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-07-23 20:54               ` Stephen Warren
2012-07-23 20:54                 ` Stephen Warren
     [not found]                 ` <500DBA1F.7050605-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-07-23 21:30                   ` Mark Brown
2012-07-23 21:30                     ` Mark Brown
2012-07-23 20:51     ` Stephen Warren
     [not found]       ` <500DB960.6020802-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-07-23 21:29         ` Mark Brown
2012-07-23 21:29           ` Mark Brown
2012-07-24  4:29         ` Laxman Dewangan
2012-07-24  4:29           ` 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=20120713142229.GM4215@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=ccross@android.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=linux-tegra@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=olof@lixom.net \
    --cc=rob.herring@calxeda.com \
    --cc=swarren@wwwdotorg.org \
    --cc=thierry.reding@avionic-design.de \
    /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.