From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] Introduce minimal irqchip infrastructure
Date: Sun, 28 Oct 2012 14:26:26 +0100 [thread overview]
Message-ID: <20121028142626.3c1ab345@skate> (raw)
In-Reply-To: <508D31EA.3050307@gmail.com>
On Sun, 28 Oct 2012 08:23:54 -0500, Rob Herring wrote:
> Other than the 2 minor things I mentioned, this series looks good.
>
> Reviewed-by: Rob Herring <rob.herring@calxeda.com>
Thanks, I'll repost a v3 once you confirm the part about "depends on
OF_IRQ".
> Also, I have some follow-on patches to move the GIC and VIC to
> drivers/irqchip. It was much more simple than I expected. I'll post them
> later.
Ah good. Aren't they some remaining non-DT users of the GIC and VIC
drivers?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2012-10-28 13:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-28 9:30 [PATCH v2] Introduce minimal irqchip infrastructure Thomas Petazzoni
2012-10-28 9:30 ` [PATCH v2 1/4] irqchip: add basic infrastructure Thomas Petazzoni
2012-10-28 13:18 ` Rob Herring
2012-10-28 13:24 ` Thomas Petazzoni
2012-10-28 13:30 ` Rob Herring
2012-10-28 13:35 ` Thomas Petazzoni
2012-10-28 9:30 ` [PATCH v2 2/4] arm: bcm2835: convert to the irqchip infrastructure Thomas Petazzoni
2012-10-28 9:30 ` [PATCH v2 3/4] arm: mvebu: move irq controller driver to drivers/irqchip Thomas Petazzoni
2012-10-28 9:41 ` Thomas Petazzoni
2012-10-28 9:42 ` Thomas Petazzoni
2012-10-28 9:30 ` [PATCH v2 4/4] irqchip: add to the directories part of the IRQ subsystem in MAINTAINERS Thomas Petazzoni
2012-10-28 13:11 ` Rob Herring
2012-10-28 13:23 ` [PATCH v2] Introduce minimal irqchip infrastructure Rob Herring
2012-10-28 13:26 ` Thomas Petazzoni [this message]
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=20121028142626.3c1ab345@skate \
--to=thomas.petazzoni@free-electrons.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.