linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: ux500: update V-INTCORE constraints
Date: Tue, 2 Apr 2013 10:24:46 +0100	[thread overview]
Message-ID: <20130402092446.GB4375@gmail.com> (raw)
In-Reply-To: <20130402084446.GA6850@balto.lan>

> > > 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.
> 
> Lee's patches are on -next

Not all of them are on -next, but all are on the MLs.

I'm currently fixing up some of Mark's review comments in order to
re-submit the remainder.

> and should not conflict with this one
> (tested again on today's tree), but it may be nice anyway to have this
> in the regulator framework with the others.

> Mark, would you consider taking this one in your tree?

-- 
Lee Jones
Linaro ST-Ericsson Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

      parent reply	other threads:[~2013-04-02  9:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-27 15:21 [PATCH] ARM: ux500: update V-INTCORE constraints Fabio Baltieri
2013-04-02  8:26 ` Linus Walleij
2013-04-02  8:38   ` Mark Brown
2013-04-02  8:44     ` Fabio Baltieri
2013-04-02  8:46       ` Mark Brown
2013-04-02  8:51         ` [PATCH RESEND] " Fabio Baltieri
2013-04-02  9:23           ` Lee Jones
2013-04-02  9:34             ` Fabio Baltieri
2013-04-02  9:24       ` Lee Jones [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=20130402092446.GB4375@gmail.com \
    --to=lee.jones@linaro.org \
    --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 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).