linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jamie@jamieiles.com (Jamie Iles)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 08/10] ARM: u300: convert to MULTI_IRQ_HANDLER
Date: Wed, 28 Sep 2011 13:29:18 +0100	[thread overview]
Message-ID: <20110928122918.GJ17204@pulham.picochip.com> (raw)
In-Reply-To: <CACRpkdarydeYAyOV8Cm134TtPeh9_qFSqWPkvpZjUE9yPNNtJA@mail.gmail.com>

On Wed, Sep 28, 2011 at 02:18:14PM +0200, Linus Walleij wrote:
> On Wed, Sep 28, 2011 at 2:03 PM, Jamie Iles <jamie@jamieiles.com> wrote:
> 
> >> vic_single_handle_irq() needs to be modified to handle several
> >> ranges or atleast two.
> >
> > The platform IRQ handler is actually vic_handle_irq() that internally
> > calls vic_single_handle_irq() for each registered vic (in the order of
> > registration).
> 
> Ah I get it I'm dead wrong as usual :-)
> 
> I tried to apply them to test but Iget into dependency trouble with
> the referenced required patches, do you have some handy
> git branch with all stuff applied in order that I can pull in and
> test off?

Sure,

	git://github.com/jamieiles/linux-2.6-ji.git vic-dt

has all of the dependencies in there too.  Thanks for taking a look at 
the patches Linus!

Jamie

  reply	other threads:[~2011-09-28 12:29 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-28 10:41 [PATCHv2 00/10] VIC DT binding and MULTI_IRQ_HANDLER Jamie Iles
2011-09-28 10:41 ` [PATCHv2 01/10] ARM: vic: device tree binding Jamie Iles
2011-09-28 20:11   ` Grant Likely
2011-09-29  4:00   ` Rob Herring
2011-09-28 10:41 ` [PATCHv2 02/10] ARM: vic: MULTI_IRQ_HANDLER handler Jamie Iles
2011-09-28 11:09   ` Linus Walleij
2011-09-28 12:08     ` Jamie Iles
2011-09-28 20:39   ` Grant Likely
2011-09-29  6:55     ` Linus Walleij
2011-09-29  9:30       ` Jamie Iles
2011-09-29 16:55         ` Grant Likely
2011-11-02 13:40         ` Russell King - ARM Linux
2011-11-02 14:08           ` Jamie Iles
2011-11-03 12:29             ` Linus Walleij
2011-11-03 12:51               ` Russell King - ARM Linux
2011-11-03 13:00                 ` Linus Walleij
2011-11-03 13:04                   ` Jamie Iles
2011-11-03 13:31                   ` Russell King - ARM Linux
2011-11-03 15:03                     ` Jamie Iles
2011-11-03 15:11                       ` Russell King - ARM Linux
2011-11-03 13:49                 ` Nicolas Pitre
2011-09-29 15:03   ` Zoltan Devai
2011-09-29 15:13     ` Jamie Iles
2011-09-28 10:41 ` [PATCHv2 03/10] ARM: ep93xx: convert to MULTI_IRQ_HANDLER Jamie Iles
2011-09-28 11:15   ` Linus Walleij
2011-09-28 10:41 ` [PATCHv2 04/10] ARM: netx: " Jamie Iles
2011-09-28 10:41 ` [PATCHv2 05/10] ARM: nomadik: " Jamie Iles
2011-09-28 11:12   ` Linus Walleij
2011-09-28 10:41 ` [PATCHv2 06/10] ARM: s3c64xx: " Jamie Iles
2011-09-28 10:41 ` [PATCHv2 07/10] ARM: spear: " Jamie Iles
2011-09-28 10:41 ` [PATCHv2 08/10] ARM: u300: " Jamie Iles
2011-09-28 11:03   ` Linus Walleij
2011-09-28 12:03     ` Jamie Iles
2011-09-28 12:18       ` Linus Walleij
2011-09-28 12:29         ` Jamie Iles [this message]
2011-09-28 10:41 ` [PATCHv2 09/10] ARM: versatile: " Jamie Iles
2011-09-28 10:41 ` [PATCHv2 10/10] ARM: samsung: " Jamie Iles

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=20110928122918.GJ17204@pulham.picochip.com \
    --to=jamie@jamieiles.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).