Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/8] Convert Ux500 to SPARSE_IRQ
Date: Fri, 19 Oct 2012 07:42:58 +0000	[thread overview]
Message-ID: <201210190742.58900.arnd@arndb.de> (raw)
In-Reply-To: <1350580695-8303-1-git-send-email-linus.walleij@stericsson.com>

On Thursday 18 October 2012, Linus Walleij wrote:
> From: Linus Walleij <linus.walleij@linaro.org>
> 
> This patch series fixes the prerequisites and then converts Ux500
> to SPARSE_IRQ.

Great stuff! In case any patches end up going through other trees,
please add my

Acked-by: Arnd Bergmann <arnd@arndb.de>

> After this series I tried turning on multiplatform for ux500
> but there are still headers in <mach/*> creating problems
> so we are still just halfway.

Which ones are still left? This is the list of inclusions I saw
in the 3.6-rc1 version of my multiplatform branch being included
from outside of the mach-ux500 directory.

I should probably redo that branch to see which ones are gone now,
but you would also catch most of these with a simple defconfig build.

      3 include <mach-ux500/board-mop500-msp.h>
      2 include <mach-ux500/crypto-ux500.h>
      1 include <mach-ux500/db8500-regs.h>
      1 include <mach-ux500/gpio.h>
      8 include <mach-ux500/hardware.h>
      3 include <mach-ux500/id.h>
      3 include <mach-ux500/irqs.h>
      1 include <mach-ux500/setup.h>
      1 include <mach-ux500/usb.h>

	Arnd

  reply	other threads:[~2012-10-19  7:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-18 17:18 [PATCH 0/8] Convert Ux500 to SPARSE_IRQ Linus Walleij
2012-10-19  7:42 ` Arnd Bergmann [this message]
2012-10-19 15:12   ` Linus Walleij

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=201210190742.58900.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox