From: Stephen Warren <swarren@wwwdotorg.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: swarren@nvidia.com, devicetree-discuss@lists.ozlabs.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH V2 0/4] ARM: tegra: dalmore: add regulators
Date: Fri, 22 Mar 2013 11:37:16 -0600 [thread overview]
Message-ID: <514C96CC.8000904@wwwdotorg.org> (raw)
In-Reply-To: <1363873663-19272-1-git-send-email-ldewangan@nvidia.com>
On 03/21/2013 07:47 AM, Laxman Dewangan wrote:
> This series add the regulators for Dalmore platform.
> Dalmore also have the Palma PMIC as primary PMIC but
> dt population will be send later once DT documentation
> finalize.
The series is applied. The first 3 patches to Tegra's for-3.10/dt
branch, and patch 4 to Tegra's for-3.10/defconfig banch.
In patch 2,
> + tps65090@48 {
I removed "@48" there, since the unit-address isn't required to make the
node name unique.
prev parent reply other threads:[~2013-03-22 17:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 13:47 [PATCH V2 0/4] ARM: tegra: dalmore: add regulators Laxman Dewangan
2013-03-21 13:47 ` [PATCH V2 1/4] ARM: tegra: dalmore: add cpu regulator node Laxman Dewangan
[not found] ` <1363873663-19272-2-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-03-21 14:07 ` Sergei Shtylyov
[not found] ` <514B1412.9060707-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2013-03-21 17:30 ` Stephen Warren
2013-03-21 13:47 ` [PATCH V2 2/4] ARM: tegra: dalmore: add TPS65090 node Laxman Dewangan
2013-03-21 13:47 ` [PATCH V2 3/4] ARM: tegra: dalmore: add fixed regulator node Laxman Dewangan
2013-03-21 13:47 ` [PATCH V2 4/4] ARM: tegra: enable Tegra114 based platform PMICs Laxman Dewangan
2013-03-22 17:37 ` 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=514C96CC.8000904@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=ldewangan@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).