All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ux500-core for ARM SoC
Date: Mon, 30 Apr 2012 21:41:08 +0000	[thread overview]
Message-ID: <201204302141.08186.arnd@arndb.de> (raw)
In-Reply-To: <1335369056-5331-1-git-send-email-linus.walleij@linaro.org>

On Wednesday 25 April 2012, Linus Walleij wrote:
> Daniel Lezcano (1):
>       ARM: ux500: add the cpuidle driver for WFI and ARM retention
> 
> Lee Jones (4):
>       ARM: ux500: Do not attempt to register non-existent i2c devices on Snowball
>       ARM: ux500: Fork cpu-db8500 platform_devs for sequential DT enablement
>       ARM: ux500: Disable SMSC911x platform code registration when DT is enabled
>       ARM: ux500: Enable PRCMU Timer 4 (clocksource) for Device Tree
> 
> Linus Walleij (4):
>       ARM: ux500: core U9540 support
>       ARM: ux500: delete U5500 support
>       mfd/db5500-prcmu: delete DB5500 PRCMU support
>       mfd/ab5500: delete AB5500 support
> 
> Michel Jaouen (1):
>       ARM: ux500: ioremap differences for DB9540
> 

Hi Linus,

Sorry for the delay in my reply. I was going to pull this but noticed
that you have an unfortunate mix of stuff in this branch, and you've done
this better in the past.

Please separate this into more logical branches, e.g.

1. delete u5500
2. add u9540 support
3. device tree patches (why not in the other branch?)

I have applied it to a staging branch for now, which means it gets
coverage in linux-next but I won't send it in the merge window without
further action.

	Arnd

  reply	other threads:[~2012-04-30 21:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-25 15:50 [GIT PULL] ux500-core for ARM SoC Linus Walleij
2012-04-30 21:41 ` Arnd Bergmann [this message]
2012-05-02 10:23   ` Linus Walleij
2012-05-02 15:40     ` Arnd Bergmann

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=201204302141.08186.arnd@arndb.de \
    --to=arnd@arndb.de \
    --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.