From: Stephen Warren <swarren@wwwdotorg.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: grant.likely@secretlab.ca, rob.herring@calxeda.com,
linux@arm.linux.org.uk, lrg@ti.com,
broonie@opensource.wolfsonmicro.com, swarren@nvidia.com,
olof@lixom.net, devicetree-discuss@lists.ozlabs.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH 0/4] regulator: tps62360: support dts and enable for tegra-cardhu
Date: Thu, 10 May 2012 12:59:12 -0600 [thread overview]
Message-ID: <4FAC1000.9070605@wwwdotorg.org> (raw)
In-Reply-To: <1336643276-16796-1-git-send-email-ldewangan@nvidia.com>
On 05/10/2012 03:47 AM, Laxman Dewangan wrote:
> Add support for dt on regulator device tps62360. Also enable this regulator for Nvidia's
> Tegra platform - cardhu.
> This series:
> - Make the regulator_init_data as pointer type from platform data.
> - enable config variable in tegra defconfig
> - add entry for tps62360 in dts file of tegra-cardhu.
The series looks fine to me. I assume patches 1 & 2 will go through the
regulator tree and I'll take patches 3 & 4 through the Tegra tree.
prev parent reply other threads:[~2012-05-10 18:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 9:47 Laxman Dewangan
2012-05-10 9:47 ` [PATCH 1/4] regulator: tps62360: make init_data of platform data to pointer Laxman Dewangan
2012-05-10 9:47 ` [PATCH 2/4] regulator: tps62360: add dt support Laxman Dewangan
2012-05-10 9:47 ` [PATCH 3/4] ARM: tegra: config: enable REGULATOR_TPS62360 Laxman Dewangan
2012-05-10 9:47 ` [PATCH 4/4] ARM: dt: tegra: cardhu: register core regulator tps62360 Laxman Dewangan
2012-05-10 18:59 ` Stephen Warren [this message]
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=4FAC1000.9070605@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=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=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=lrg@ti.com \
--cc=olof@lixom.net \
--cc=rob.herring@calxeda.com \
--cc=swarren@nvidia.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
all inboxes | Powered by JetHome®