From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH 1/2] arm: Kconfig: select correct HAVE_SPARSE_IRQ symbol
Date: Wed, 15 Jun 2011 16:02:39 +0300 [thread overview]
Message-ID: <1308142960-20767-2-git-send-email-balbi@ti.com> (raw)
In-Reply-To: <1308142960-20767-1-git-send-email-balbi@ti.com>
commit e2a93ecc7fc469dab52323c11a2d8ceaa62aac7b
(ARM: Use genirq definitions from kernel/irq/Kconfig)
made ARM Kconfig use the generic Kconfig symbols from
kernel/irq/Kconfig but did not fix the boards which
were using the older symbols, fix them.
Signed-off-by: Felipe Balbi <balbi@ti.com>
---
arch/arm/Kconfig | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index 9adc278..a061525 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -545,7 +545,7 @@ config ARCH_MMP
select HAVE_SCHED_CLOCK
select TICK_ONESHOT
select PLAT_PXA
- select SPARSE_IRQ
+ select HAVE_SPARSE_IRQ
help
Support for Marvell's PXA168/PXA910(MMP) and MMP2 processor line.
@@ -617,7 +617,7 @@ config ARCH_PXA
select HAVE_SCHED_CLOCK
select TICK_ONESHOT
select PLAT_PXA
- select SPARSE_IRQ
+ select HAVE_SPARSE_IRQ
help
Support for Intel/Marvell's PXA2xx/PXA3xx processor line.
--
1.7.6.rc1
next prev parent reply other threads:[~2011-06-15 13:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 13:02 [RESEND PATCH 0/2] ARM IRQ Kconfig patches Felipe Balbi
2011-06-15 13:02 ` Felipe Balbi [this message]
2011-06-15 13:02 ` [RESEND PATCH 2/2] arm: Kconfig: allow OMAP to use sparse IRQ numbering Felipe Balbi
2011-06-15 15:14 ` [RESEND PATCH 0/2] ARM IRQ Kconfig patches Russell King - ARM Linux
2011-06-15 15:24 ` Felipe Balbi
2011-06-16 9:19 ` Felipe Balbi
2011-06-15 23:48 ` Kevin Hilman
2011-06-16 11:49 ` Sergei Shtylyov
2011-06-16 21:40 ` Russell King - ARM Linux
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=1308142960-20767-2-git-send-email-balbi@ti.com \
--to=balbi@ti.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).