From: davidb@codeaurora.org (David Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/3] genirq: handling GIC per-cpu interrupts
Date: Mon, 26 Sep 2011 13:18:36 -0700 [thread overview]
Message-ID: <20110926201836.GA27355@huya.qualcomm.com> (raw)
In-Reply-To: <1316793788-14500-1-git-send-email-marc.zyngier@arm.com>
On Fri, Sep 23, 2011 at 05:03:05PM +0100, Marc Zyngier wrote:
> Tested on ARM Versatile Express (Cortex A15), ARM RealView PB11MP,
> OMAP4 (Panda) and Tegra (Harmony). Patch series against next-20110923.
>
> From v2:
> - Fixed !GENERIC_HARDIRQS build
> - Fixed request_percpu_irq documentation
>
> From v1:
> - General tidy-up after Thomas' review. I've kept the config option
> for the time being until we can sort out the anonymous union
> problem.
>
> Marc Zyngier (3):
> genirq: add support for per-cpu dev_id interrupts
> ARM: gic: consolidate PPI handling
> ARM: gic, local timers: use the request_percpu_irq() interface
I've tested this on an MSM8660 based off of next-20110926.
Tested-by: David Brown <davidb@codeaurora.org>
Acked-by: David Brown <davidb@codeaurora.org>
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2011-09-26 20:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 16:03 [PATCH v3 0/3] genirq: handling GIC per-cpu interrupts Marc Zyngier
2011-09-23 16:03 ` [PATCH v3 1/3] genirq: add support for per-cpu dev_id interrupts Marc Zyngier
2011-09-29 5:56 ` Abhijeet Dharmapurikar
2011-09-30 11:08 ` Marc Zyngier
2011-09-23 16:03 ` [PATCH v3 2/3] ARM: gic: consolidate PPI handling Marc Zyngier
2011-09-28 0:59 ` Tony Lindgren
2011-09-23 16:03 ` [PATCH v3 3/3] ARM: gic, local timers: use the request_percpu_irq() interface Marc Zyngier
2011-09-26 20:18 ` David Brown [this message]
2011-09-27 0:11 ` [PATCH v3 0/3] genirq: handling GIC per-cpu interrupts David Brown
2011-09-27 10:21 ` 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=20110926201836.GA27355@huya.qualcomm.com \
--to=davidb@codeaurora.org \
--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).