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: Mon, 20 Aug 2012 18:54:10 +0100 [thread overview]
Message-ID: <20120820175410.GI26991@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <50327897.5030601@wwwdotorg.org>
[-- Attachment #1: Type: text/plain, Size: 649 bytes --]
On Mon, Aug 20, 2012 at 11:49:11AM -0600, Stephen Warren wrote:
> The problem there is that will prevent any regulators from being
> registered at all, until the patch is merged with the regulator tree.
> That will also prevent PCIe working on Harmony. Those both work right
> now, so that's a bisection breakage.
> I suppose the solution here is to merge the regulator tree into the
> Tegra branch before the Harmony regulator patch. Mark, can we do that?
I've no idea what you're talking about here, sorry. What are "this" and
"the patch"? Surely you can just add whatever DT changes you need to
add without the thing that uses the bindings?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-08-20 17:54 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 [this message]
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
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=20120820175410.GI26991@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).