From: Stephen Warren <swarren@wwwdotorg.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
"ccross@android.com" <ccross@android.com>,
"olof@lixom.net" <olof@lixom.net>, "lrg@ti.com" <lrg@ti.com>,
"thierry.reding@avionic-design.de"
<thierry.reding@avionic-design.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>
Subject: Re: [PATCH 2/2] regulator: tps6586x: add support for input supply
Date: Mon, 23 Jul 2012 14:54:55 -0600 [thread overview]
Message-ID: <500DBA1F.7050605@wwwdotorg.org> (raw)
In-Reply-To: <20120715212114.GI4041@opensource.wolfsonmicro.com>
On 07/15/2012 03:21 PM, Mark Brown wrote:
> On Fri, Jul 13, 2012 at 10:45:12PM +0530, Laxman Dewangan wrote:
>
>> I was thinking that 1/2 should also go through your tree to
>> avoid any functionality break on existing platform who are using
>> this regulator.
>
> I'd be happy to do that if the ARM people are happy with it; just
> let me know and resend the patch if you want me to apply it.
Patch 2/2 really depends on patch 1/2 to avoid git bisect breakage;
are you able to rebase it to maintain that order when applying it?
next prev parent reply other threads:[~2012-07-23 20:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 13:50 [PATCH 0/2] regulator: tps6586x: " Laxman Dewangan
2012-07-13 13:50 ` [PATCH 1/2] ARM: tegra: harmony: add regulator supply name and its " Laxman Dewangan
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 14:22 ` Mark Brown
2012-07-13 17:15 ` Laxman Dewangan
2012-07-15 21:21 ` Mark Brown
2012-07-23 20:54 ` Stephen Warren [this message]
2012-07-23 21:30 ` Mark Brown
2012-07-23 20:51 ` Stephen Warren
2012-07-23 21:29 ` Mark Brown
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=500DBA1F.7050605@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome