Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: tglx@linutronix.de (Thomas Gleixner)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v3 1/3] genirq: introduce CONFIG_GENERIC_IRQ_MIGRATION
Date: Wed, 16 Sep 2015 10:13:06 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.11.1509161011371.3951@nanos> (raw)
In-Reply-To: <1442375907-11496-2-git-send-email-yangyingliang@huawei.com>

On Wed, 16 Sep 2015, Yang Yingliang wrote:
> diff --git a/arch/arc/Kconfig b/arch/arc/Kconfig
> index 78c0621..4133070 100644
> --- a/arch/arc/Kconfig
> +++ b/arch/arc/Kconfig
> @@ -20,6 +20,7 @@ config ARC
>  	# for now, we don't need GENERIC_IRQ_PROBE, CONFIG_GENERIC_IRQ_CHIP
>  	select GENERIC_IRQ_SHOW
>  	select GENERIC_PENDING_IRQ if SMP
> +	select GENERIC_IRQ_MIGRATION if SMP

What's the point of this?

> --- a/kernel/irq/Kconfig
> +++ b/kernel/irq/Kconfig
> @@ -30,6 +30,10 @@ config GENERIC_IRQ_LEGACY_ALLOC_HWIRQ
>  config GENERIC_PENDING_IRQ
>  	bool

+	select GENERIC_IRQ_MIGRATION

Will do it automatically without touching any of the arch Kconfig
files.

Thanks,

	tglx

  reply	other threads:[~2015-09-16  8:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-16  3:58 [RFC PATCH v3 0/3] arm/arm64: fix a migrating irq bug when hotplug cpu Yang Yingliang
2015-09-16  3:58 ` [RFC PATCH v3 1/3] genirq: introduce CONFIG_GENERIC_IRQ_MIGRATION Yang Yingliang
2015-09-16  8:13   ` Thomas Gleixner [this message]
2015-09-16 11:07     ` Yang Yingliang
2015-09-16  3:58 ` [RFC PATCH v3 2/3] ia64: rename migrate_irqs() to avoid compiling error Yang Yingliang
2015-09-16  8:21   ` Thomas Gleixner
2015-09-16 11:13     ` Yang Yingliang
2015-09-16  3:58 ` [RFC PATCH v3 3/3] arm/arm64: fix a migrating irq bug when hotplug cpu Yang Yingliang
2015-09-16  8:21   ` Thomas Gleixner
2015-09-16 11:15     ` Yang Yingliang

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=alpine.DEB.2.11.1509161011371.3951@nanos \
    --to=tglx@linutronix.de \
    --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