linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 11/13] ARM: only include mach/irqs.h for !SPARSE_IRQ
Date: Wed, 25 Jan 2012 22:58:17 +0000	[thread overview]
Message-ID: <201201252358.17825.marek.vasut@gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1201251727510.2759@xanadu.home>

> On Wed, 25 Jan 2012, Russell King - ARM Linux wrote:
> > As a side-note, you may be pleased to know that I have SA11x0 stuff
> > converted to (and tested) with sparse IRQ.  That's with SA1111, the
> > UCB1x00 and Neponset expansion board for the Assabet all dynamically
> > allocating their IRQs.  The only fixed-numbered IRQs in SA11x0 in my
> > tree at the time of writing are the on-SoC IRQs, and the LoCoMo IRQs
> > (which I don't have the hardware to test for, so I'm not touching.)
> 
> That's really cool.
> 
> Not that there are many people who might still benefit from running that
> code, but like I said this should serve as a real and relatively simple
> example that might benefit more complex platforms.
> 
> 
> Nicolas

Indeed, that's good going. I'm CCing a guy who might have a SA11xx board with 
LoCoMo chip (that's old zaurus sl55xx, right?).

  reply	other threads:[~2012-01-25 22:58 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-20 20:32 [PATCH v2 00/13] Make mach/irqs.h optional Rob Herring
2012-01-20 20:32 ` [PATCH v2 01/13] sound: pxa2xx-ac97: include mach/irqs.h directly Rob Herring
2012-01-20 20:33 ` [PATCH v2 02/13] gpio: pxa: explicitly include mach/irqs.h Rob Herring
2012-01-20 20:33 ` [PATCH v2 03/13] ARM: remove mc146818rtc.h from time.c Rob Herring
2012-01-20 20:33 ` [PATCH v2 04/13] ARM: mc146818rtc: remove unnecessary include of mach/irqs.h Rob Herring
2012-01-20 20:33 ` [PATCH v2 05/13] ARM: it8152: explicitly include mach/irqs.h Rob Herring
2012-01-20 20:33 ` [PATCH v2 06/13] sh: intc: unify evt2irq/irq2evt macros for sh and arm Rob Herring
2012-01-20 20:33 ` [PATCH v2 07/13] sh: intc: remove dependency on NR_IRQS Rob Herring
2012-01-20 20:33 ` [PATCH v2 08/13] ARM: mmp: remove NR_IRQS Rob Herring
2012-01-20 20:33 ` [PATCH v2 09/13] ARM: pxa: " Rob Herring
2012-01-20 20:33 ` [PATCH v2 10/13] ARM: shmobile: " Rob Herring
2012-01-20 20:33 ` [PATCH v2 11/13] ARM: only include mach/irqs.h for !SPARSE_IRQ Rob Herring
2012-01-20 21:11   ` Nicolas Pitre
2012-01-20 21:23     ` Rob Herring
2012-01-20 22:48       ` Nicolas Pitre
2012-01-25 19:23         ` Rob Herring
2012-01-30 15:01           ` Grant Likely
2012-01-30 16:33             ` Rob Herring
2012-01-25 21:32       ` Russell King - ARM Linux
2012-01-25 22:32         ` Nicolas Pitre
2012-01-25 22:58           ` Marek Vasut [this message]
2012-01-30 10:44             ` Cyril Hrubis
2012-02-01 10:03               ` Pavel Machek
2012-01-20 20:33 ` [PATCH v2 12/13] ARM: highbank: select SPARSE_IRQ and remove irqs.h Rob Herring
2012-01-20 20:33 ` [PATCH v2 13/13] ARM: picoxcell: remove mach/irqs.h Rob Herring
2012-02-16  8:45 ` [PATCH v2 00/13] Make mach/irqs.h optional Russell King - ARM Linux
2012-02-16  9:05   ` Russell King - ARM Linux
2012-02-16 13:29     ` Rob Herring

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=201201252358.17825.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).