From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/15] arch/arm/mach-* late_initcall cleanup
Date: Fri, 4 May 2012 16:56:55 -0700 [thread overview]
Message-ID: <20120504235655.GC5613@atomide.com> (raw)
In-Reply-To: <20120502133757.GB2194@S2101-09.ap.freescale.net>
* Shawn Guo <shawn.guo@linaro.org> [120502 06:41]:
> On Wed, May 02, 2012 at 12:45:02PM +0000, Arnd Bergmann wrote:
> > On Wednesday 02 May 2012, Shawn Guo wrote:
> > > This series tries to clean up those late_initcall in arch/arm/mach-*,
> > > which will be a blocker for single kernel build for multiple platforms.
> > > Even on single platform, for example imx, where we already have single
> > > kernel image for imx3, imx5 and imx6 families, late_initcall does not
> > > scale. We have to detect soc type in the late_initcall to do soc
> > > sepcific late initialization.
> >
> > Hi Shawn,
> >
> > If you're targetting this at v3.5, I think we should get it into arm-soc
> > as a staging branch to give it some more testing in linux-next ASAP.
> >
> Thanks for the reminding, Arnd. Yes, I'm targeting this at v3.5,
> since the imx cpuidle drivers from Rob Lee which targets at v3.5
> depends on it.
Sorro for being late in responding, these look good to me. For the
omap parts:
Acked-by: Tony Lindgren <tony@atomide.com>
Also ack to merge without my ack added for being late ;)
Tony
next prev parent reply other threads:[~2012-05-04 23:56 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 11:33 [PATCH 00/15] arch/arm/mach-* late_initcall cleanup Shawn Guo
2012-05-02 11:33 ` [PATCH 01/15] ARM: provide a late_initcall hook for platform initialization Shawn Guo
2012-05-02 13:14 ` Shawn Guo
2012-05-03 14:55 ` Shawn Guo
2012-05-03 14:58 ` Russell King - ARM Linux
2012-05-02 17:47 ` H Hartley Sweeten
2012-05-02 11:33 ` [PATCH 02/15] ARM: davinci: use machine specific hook for late init Shawn Guo
2012-05-04 19:58 ` Sekhar Nori
2012-05-05 6:27 ` Shawn Guo
2012-05-02 11:33 ` [PATCH 03/15] ARM: ep93xx: " Shawn Guo
2012-05-02 17:45 ` H Hartley Sweeten
2012-05-03 15:05 ` Shawn Guo
2012-05-02 11:33 ` [PATCH 04/15] ARM: exynos: " Shawn Guo
2012-05-02 11:33 ` [PATCH 05/15] ARM: imx: " Shawn Guo
2012-05-02 12:36 ` Sascha Hauer
2012-05-02 11:33 ` [PATCH 06/15] ARM: msm: " Shawn Guo
2012-05-02 18:28 ` David Brown
2012-05-02 11:33 ` [PATCH 07/15] ARM: omap1: " Shawn Guo
2012-05-02 11:33 ` [PATCH 08/15] ARM: omap2: " Shawn Guo
2012-05-02 11:33 ` [PATCH 09/15] ARM: pnx4008: " Shawn Guo
2012-05-02 11:33 ` [PATCH 10/15] ARM: prima2: " Shawn Guo
2012-05-02 11:33 ` [PATCH 11/15] ARM: s3c64xx: " Shawn Guo
2012-05-02 11:33 ` [PATCH 12/15] ARM: sa1100: " Shawn Guo
2012-05-02 11:33 ` [PATCH 13/15] ARM: shmobile: " Shawn Guo
2012-05-02 11:33 ` [PATCH 14/15] ARM: tegra: " Shawn Guo
2012-05-02 15:57 ` Stephen Warren
2012-05-02 11:33 ` [PATCH 15/15] ARM: ux500: " Shawn Guo
2012-05-07 12:19 ` Linus Walleij
2012-05-08 12:39 ` Shawn Guo
2012-05-02 12:45 ` [PATCH 00/15] arch/arm/mach-* late_initcall cleanup Arnd Bergmann
2012-05-02 13:37 ` Shawn Guo
2012-05-02 13:41 ` Arnd Bergmann
2012-05-04 23:56 ` Tony Lindgren [this message]
2012-05-05 6:25 ` Shawn Guo
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=20120504235655.GC5613@atomide.com \
--to=tony@atomide.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.