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: [tip:irq/core] genirq: Introduce generic irq migration for cpu hotunplug
Date: Thu, 1 Oct 2015 16:24:24 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.11.1510011619390.4500@nanos> (raw)
In-Reply-To: <tip-f1e0bb0ad473a32d1b7e6d285ae9f7e47710bb5e@git.kernel.org>

On Thu, 1 Oct 2015, tip-bot for Yang Yingliang wrote:

> Commit-ID:  f1e0bb0ad473a32d1b7e6d285ae9f7e47710bb5e
> Gitweb:     http://git.kernel.org/tip/f1e0bb0ad473a32d1b7e6d285ae9f7e47710bb5e
> Author:     Yang Yingliang <yangyingliang@huawei.com>
> AuthorDate: Thu, 24 Sep 2015 17:32:13 +0800
> Committer:  Thomas Gleixner <tglx@linutronix.de>
> CommitDate: Thu, 1 Oct 2015 14:51:15 +0200
> 
> genirq: Introduce generic irq migration for cpu hotunplug
> 
> ARM and ARM64 have almost identical code for migrating interrupts on
> cpu hotunplug. Provide a generic version which can be used by both.
> 
> The new code addresses a shortcoming in the ARM[64] variants which
> fails to update the affinity change in some cases. The solution for
> this is to use the core function irq_do_set_affinity() instead of open
> coding it.
> 
> [ tglx: Added copyright notice and license boilerplate. Rewrote
>   	subject and changelog. ]
> 
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
> Acked-by: Russell King - ARM Linux <linux@arm.linux.org.uk>
> Cc: Jiang Liu <jiang.liu@linux.intel.com>
> Cc: Marc Zyngier <marc.zyngier@arm.com>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Will Deacon <will.deacon@arm.com>
> Cc: Hanjun Guo <hanjun.guo@linaro.org>
> Cc: <linux-arm-kernel@lists.infradead.org>
> Link: http://lkml.kernel.org/r/1443087135-17044-2-git-send-email-yangyingliang at huawei.com
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>

Russell, Will,

I applied that to a seperate branch

  git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq/for-arm

You can pull that into arm[64] so you can apply the architecture
specific part.

Thanks,

	tglx

  parent reply	other threads:[~2015-10-01 14:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24  9:32 [RFC PATCH v6 0/3] arm/arm64: fix a migrating irq bug when hotplug cpu Yang Yingliang
2015-09-24  9:32 ` [RFC PATCH v6 1/3] genirq: introduce CONFIG_GENERIC_IRQ_MIGRATION and kernel/irq/cpuhotplug.c Yang Yingliang
     [not found]   ` <tip-f1e0bb0ad473a32d1b7e6d285ae9f7e47710bb5e@git.kernel.org>
2015-10-01 14:24     ` Thomas Gleixner [this message]
2015-10-01 14:47       ` [tip:irq/core] genirq: Introduce generic irq migration for cpu hotunplug Catalin Marinas
2015-09-24  9:32 ` [RFC PATCH v6 2/3] arm64: fix a migrating irq bug when hotplug cpu Yang Yingliang
2015-10-09 16:55   ` Catalin Marinas
2015-09-24  9:32 ` [RFC PATCH v6 3/3] arm: " Yang Yingliang
2015-10-13 19:28   ` Russell King - ARM Linux
2015-10-21 11:47   ` Geert Uytterhoeven
2015-10-21 20:29     ` Russell King - ARM Linux
2015-10-22  9:26       ` Russell King - ARM Linux
2015-10-22  9:46         ` Geert Uytterhoeven
2015-10-22 10:56         ` Yang Yingliang
2015-10-22 11:13           ` Russell King - ARM Linux
2015-10-22 12:43             ` Thomas Gleixner
2015-10-22 16:34               ` Catalin Marinas
2015-12-15  6:59             ` 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.1510011619390.4500@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