From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
Stephen Warren <swarren@nvidia.com>,
"olof@lixom.net" <olof@lixom.net>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] ARM: dt: tegra: harmony: add regulators
Date: Wed, 22 Aug 2012 20:07:15 +0100 [thread overview]
Message-ID: <20120822190714.GF7995@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <503283F8.4070808@wwwdotorg.org>
[-- Attachment #1: Type: text/plain, Size: 680 bytes --]
On Mon, Aug 20, 2012 at 12:37:44PM -0600, Stephen Warren wrote:
> On 08/20/2012 12:14 PM, Mark Brown wrote:
> > Why not just pull the patch in via the regulator tree? The idea
> > of merging the entire regulator drivers branch into the Tegra tree
> > doesn't seem awesome...
> I think that'd end up causing some annoying conflicts with other
> changes that also touch arch/arm/match-tegra/board-dt-tegra20.c.
> Perhaps they're manageable; they probably aren't that bad, but it
> seems better to avoid them.
Ugh, right. I guess I'd best rebase the commits out of the drivers
branch. Can you let me know what you depend on and I'll build a
mergable branch for you to pull in?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-08-22 19:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 6:59 [PATCH] ARM: dt: tegra: harmony: add regulators Laxman Dewangan
2012-08-17 19:27 ` Stephen Warren
2012-08-17 19:55 ` Stephen Warren
2012-08-20 17:22 ` Laxman Dewangan
2012-08-20 17:49 ` Stephen Warren
2012-08-20 17:54 ` Mark Brown
2012-08-20 18:08 ` Stephen Warren
2012-08-20 18:14 ` Mark Brown
2012-08-20 18:37 ` Stephen Warren
2012-08-22 19:07 ` Mark Brown [this message]
2012-08-24 18:53 ` Stephen Warren
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=20120822190714.GF7995@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=ldewangan@nvidia.com \
--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=swarren@nvidia.com \
--cc=swarren@wwwdotorg.org \
/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).