linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: vexpress: Enable selection of SPARSE_IRQ
Date: Wed, 13 Jun 2012 14:23:05 -0500	[thread overview]
Message-ID: <4FD8E899.8080207@gmail.com> (raw)
In-Reply-To: <1339607602-3846-3-git-send-email-tixy@linaro.org>

On 06/13/2012 12:13 PM, Jon Medhurst (Tixy) wrote:
> From: Jon Medhurst <tixy@linaro.org>
> 
> This is required to add vexpress to multiplatform kernels containing
> other boards which require SPARSE_IRQ.
> 
> Signed-off-by: Jon Medhurst <tixy@linaro.org>
> ---
>  arch/arm/Kconfig |    1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
> index 84449dd..bdede09 100644
> --- a/arch/arm/Kconfig
> +++ b/arch/arm/Kconfig
> @@ -311,6 +311,7 @@ config ARCH_VEXPRESS
>  	select HAVE_CLK
>  	select HAVE_PATA_PLATFORM
>  	select ICST
> +	select MAY_HAVE_SPARSE_IRQ

Why not always select SPARSE_IRQ and remove mach/irqs.h?

Rob

>  	select NO_IOPORT
>  	select PLAT_VERSATILE
>  	select PLAT_VERSATILE_CLCD

  reply	other threads:[~2012-06-13 19:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-13 17:13 [PATCH 0/2] ARM: vexpress: Enable SPARSE_IRQ selection Jon Medhurst (Tixy)
2012-06-13 17:13 ` [PATCH 1/2] ARM: vexpress: Remove IRQ defines from mach/irq.h Jon Medhurst (Tixy)
2012-06-13 17:13 ` [PATCH 2/2] ARM: vexpress: Enable selection of SPARSE_IRQ Jon Medhurst (Tixy)
2012-06-13 19:23   ` Rob Herring [this message]
2012-06-14  7:32     ` Jon Medhurst (Tixy)
2012-06-14  8:55 ` [PATCH 0/2] ARM: vexpress: Enable SPARSE_IRQ selection Russell King - ARM Linux
2012-06-14 11:33   ` Jon Medhurst (Tixy)
2012-06-14 11:43     ` [PATCH v2] ARM: vexpress: Enable SPARSE_IRQ Jon Medhurst (Tixy)

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=4FD8E899.8080207@gmail.com \
    --to=robherring2@gmail.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).