All of lore.kernel.org
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ux500 DT related fixes and platform enhancements
Date: Wed, 6 Feb 2013 09:48:09 -0800	[thread overview]
Message-ID: <CAOesGMiJTcjdEJzSDkpdV-ZCqN24uVmfjM-HOt+ojErS=98TmQ@mail.gmail.com> (raw)
In-Reply-To: <20130206135911.GB7519@gmail.com>

Hi,

On Wed, Feb 6, 2013 at 5:59 AM, Lee Jones <lee.jones@linaro.org> wrote:

> Lee Jones (14):
>       ARM: ux500: Change IRQ from low-to-high edge triggered to high-to-low
>       ARM: ux500: Include the PRCMU's Secure Registers in DB8500's DT
>       ARM: ux500: Provide a means to obtain the SMSC9115 clock when DT is enabled
>       clk: ux500: Ensure the FMSC clock is obtainable
>       clk: ux500: Provide an alias for the SMSC911x Ethernet chip
>       net/smsc911x: Provide common clock functionality
>       mmc: mmci: Move ios_handler functionality into the driver

This patch lacks acks from MMC maintainers. Actually, it should just
be submitted like any other MMC patches; to Chris Ball and the MMC
list.

>       ARM: ux500: Set correct MMCI regulator voltages in the ux5x0 Device Tree
>       ARM: ux500: Specify the ux5x0 MMCI regulator's on/off GPIO as high-enable
>       ARM: ux500: Specify which IOS regulator to use for MMCI
>       ARM: ux500: Use the correct name when supplying a GPIO enable pin
>       ARM: ux500: Setup correct settling time for the MMCI regulator
>       ARM: ux500: Use the GPIO regulator framework for SDI0's 'en' and 'vsel'
>       ARM: ux500: Remove traces of the ios_handler from platform code

So, the most of these patches really are just ux500 platform patches.
Please start queuing these through the ux500 maintainers, i.e. Linus
and Srinidhi. We've had cases in the past where you and him step on
each others toes (as with the mach/id.h removal), due to lack of
coordination. It's definitely easier for everyone if the patches come
through (and get acked by) one entity.

The obvious way of doing this is to make sure that Linus (and
Srinidhi) are in control of what's going in and when, so they can
resolve conflicts and not have them break the whole platform for
everybody due to changes they have been unaware of.


-Olof

       reply	other threads:[~2013-02-06 17:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130131115552.GG5301@gmail.com>
     [not found] ` <20130206135911.GB7519@gmail.com>
2013-02-06 17:48   ` Olof Johansson [this message]
2013-02-06 22:28     ` [GIT PULL] ux500 DT related fixes and platform enhancements Linus Walleij
2013-02-07  2:35       ` Chris Ball
     [not found]     ` <CAF2Aj3gaFtPs7gLd3snzVr1a8Px5A_RN1vz=M+U_LZ3MBpyqqw@mail.gmail.com>
2013-02-07 18:54       ` Linus Walleij
2013-02-08  8:31         ` Lee Jones
2013-02-10 15:08           ` Linus Walleij
2013-02-11  8:32             ` 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='CAOesGMiJTcjdEJzSDkpdV-ZCqN24uVmfjM-HOt+ojErS=98TmQ@mail.gmail.com' \
    --to=olof@lixom.net \
    --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.