From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/14] Ux500 multiplatform v2
Date: Sun, 7 Apr 2013 23:04:45 +0200 [thread overview]
Message-ID: <201304072304.46159.arnd@arndb.de> (raw)
In-Reply-To: <20130407205216.GB24058@zurbaran>
On Sunday 07 April 2013, Samuel Ortiz wrote:
> On Fri, Apr 05, 2013 at 05:13:54PM +0200, Arnd Bergmann wrote:
> > On Friday 05 April 2013, Linus Walleij wrote:
> I am fine with Linus' changes. Would it be possible for you to setup a branch
> where I could also pull those changes from ? Or are the interdependencies too
> strong to do so ?
Sure, I always create a stable branch for each pull request I get for this
purpose anyway. Actually it might be nice if Linus could produce two branches:
One that has the MFD changes only, and the second one based on the first that
adds all the remaining changes. Then you can pull in just the first branch
and don't need to add too many changes outside of drivers/mfd to your tree.
I don't think that the patches depend on anything that is already in arm-soc,
but we might need to add other changes on top.
Arnd
next prev parent reply other threads:[~2013-04-07 21:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 14:22 [PATCH 00/14] Ux500 multiplatform v2 Linus Walleij
2013-04-05 14:22 ` [PATCH 01/14] ARM: ux500: move debugmacro to debug includes Linus Walleij
2013-04-05 14:22 ` [PATCH 02/14] clk: ux500: pass clock base adresses in init call Linus Walleij
2013-04-05 14:22 ` [PATCH 03/14] ARM: ux500: move mach/msp.h to <linux/platform_data/*> Linus Walleij
2013-04-05 14:22 ` [PATCH 04/14] staging: ste_rmi4: kill platform_data hack Linus Walleij
2013-04-05 14:22 ` [PATCH 05/14] mfd: prcmu: pass a base and size with the early initcall Linus Walleij
2013-04-05 14:22 ` [PATCH 06/14] mfd: db8500-prcmu: get base address from resource Linus Walleij
2013-04-05 14:22 ` [PATCH 07/14] ARM: ux500: move PM-related PRCMU functions to machine Linus Walleij
2013-04-05 14:22 ` [PATCH 08/14] ARM: ux500: make debug macro stand-alone Linus Walleij
2013-04-05 14:22 ` [PATCH 09/14] ARM: ux500: get rid of <mach/[hardware|db8500-regs].h> Linus Walleij
2013-04-05 14:22 ` [PATCH 10/14] ARM: ux500: split out prcmu initialization Linus Walleij
2013-04-05 14:22 ` [PATCH 11/14] ARM: ux500: make irqs.h local to platform Linus Walleij
2013-04-05 14:22 ` [PATCH 12/14] ARM: ux500: make remaining headers local Linus Walleij
2013-04-05 14:22 ` [PATCH 13/14] ARM: ux500: move to multiplatform Linus Walleij
2013-04-05 14:22 ` [PATCH 14/14] ARM: ux500: build hotplug.o for ARMv7-a Linus Walleij
2013-04-05 15:13 ` [PATCH 00/14] Ux500 multiplatform v2 Arnd Bergmann
2013-04-07 20:52 ` Samuel Ortiz
2013-04-07 21:04 ` Arnd Bergmann [this message]
2013-04-07 21:46 ` Samuel Ortiz
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=201304072304.46159.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.