From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: ux500: update V-INTCORE constraints
Date: Tue, 2 Apr 2013 09:38:30 +0100 [thread overview]
Message-ID: <20130402083829.GB23065@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CACRpkdYgCxf9R1aU2QdPUBxErhK=E2tM=6L-yMLA_L3+ntj3nQ@mail.gmail.com>
On Tue, Apr 02, 2013 at 10:26:12AM +0200, Linus Walleij wrote:
> I know that Lee's been sending off a large set of regulator patches
> lately, some include alterations to this platform config.
> Maybe it's better to take this patch into the regulator tree if these
> machine configs will come in that way? Also like Lee to have a
> look at this...
If it's touching the board constraints it's likely to have conflicts
with Lee's stuff, yes.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130402/1decce6c/attachment-0001.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Fabio Baltieri <fabio.baltieri@linaro.org>,
Lee Jones <lee.jones@linaro.org>,
Srinidhi Kasagar <srinidhi.kasagar@stericsson.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: ux500: update V-INTCORE constraints
Date: Tue, 2 Apr 2013 09:38:30 +0100 [thread overview]
Message-ID: <20130402083829.GB23065@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CACRpkdYgCxf9R1aU2QdPUBxErhK=E2tM=6L-yMLA_L3+ntj3nQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 443 bytes --]
On Tue, Apr 02, 2013 at 10:26:12AM +0200, Linus Walleij wrote:
> I know that Lee's been sending off a large set of regulator patches
> lately, some include alterations to this platform config.
> Maybe it's better to take this patch into the regulator tree if these
> machine configs will come in that way? Also like Lee to have a
> look at this...
If it's touching the board constraints it's likely to have conflicts
with Lee's stuff, yes.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-04-02 8:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 15:21 [PATCH] ARM: ux500: update V-INTCORE constraints Fabio Baltieri
2013-03-27 15:21 ` Fabio Baltieri
2013-04-02 8:26 ` Linus Walleij
2013-04-02 8:26 ` Linus Walleij
2013-04-02 8:38 ` Mark Brown [this message]
2013-04-02 8:38 ` Mark Brown
2013-04-02 8:44 ` Fabio Baltieri
2013-04-02 8:44 ` Fabio Baltieri
2013-04-02 8:46 ` Mark Brown
2013-04-02 8:46 ` Mark Brown
2013-04-02 8:51 ` [PATCH RESEND] " Fabio Baltieri
2013-04-02 8:51 ` Fabio Baltieri
2013-04-02 9:23 ` Lee Jones
2013-04-02 9:23 ` Lee Jones
2013-04-02 9:34 ` Fabio Baltieri
2013-04-02 9:34 ` Fabio Baltieri
2013-04-02 9:24 ` [PATCH] " Lee Jones
2013-04-02 9:24 ` Lee Jones
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=20130402083829.GB23065@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.