From: adharmap@codeaurora.org
To: linux-arm-kernel@lists.infradead.org
Cc: Russell King <linux@arm.linux.org.uk>,
Abhijeet Dharmapurikar <adharmap@quicinc.com>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
linux-omap@vger.kernel.org, Yinghai Lu <yinghai@kernel.org>,
linux-arm-msm@lists.infradead.org
Subject: [PATCH v2 2/4] GIC: Prevent gic from crossing NR_IRQS
Date: Thu, 28 Jan 2010 23:06:02 -0800 [thread overview]
Message-ID: <1264748764-5319-3-git-send-email-adharmap@codeaurora.org> (raw)
In-Reply-To: <1264748764-5319-1-git-send-email-adharmap@codeaurora.org>
From: Abhijeet Dharmapurikar <adharmap@quicinc.com>
Prevent gic code from initializing interrupts beyon NR_IRQS.
Signed-off-by: Abhijeet Dharmapurikar <adharmap@quicinc.com>
---
arch/arm/common/gic.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/arch/arm/common/gic.c b/arch/arm/common/gic.c
index cd92ce0..8a2bfae 100644
--- a/arch/arm/common/gic.c
+++ b/arch/arm/common/gic.c
@@ -237,7 +237,8 @@ void __init gic_dist_init(unsigned int gic_nr, void __iomem *base,
/*
* Setup the Linux IRQ subsystem.
*/
- for (i = irq_start; i < gic_data[gic_nr].irq_offset + max_irq; i++) {
+ for (i = irq_start;
+ i < NR_IRQS && i < gic_data[gic_nr].irq_offset + max_irq; i++) {
set_irq_chip(i, &gic_chip);
set_irq_chip_data(i, &gic_data[gic_nr]);
set_irq_handler(i, handle_level_irq);
--
1.5.6.3
next prev parent reply other threads:[~2010-01-29 7:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 7:06 [PATCH v2 0/4] GIC Changes adharmap
2010-01-29 7:06 ` [PATCH v2 1/4] GIC: Disable unused interrupts adharmap
2010-01-29 7:06 ` adharmap [this message]
2010-01-29 7:06 ` [PATCH v2 3/4] GIC: Add callback for mask_ack adharmap
2010-01-29 7:06 ` [PATCH v2 4/4] GIC: Dont disable INT in ack callback adharmap
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=1264748764-5319-3-git-send-email-adharmap@codeaurora.org \
--to=adharmap@codeaurora.org \
--cc=adharmap@quicinc.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mingo@elte.hu \
--cc=yinghai@kernel.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