On Thu, Oct 01, 2015 at 04:24:24PM +0200, Thomas Gleixner wrote: > On Thu, 1 Oct 2015, tip-bot for Yang Yingliang wrote: > > > Commit-ID: f1e0bb0ad473a32d1b7e6d285ae9f7e47710bb5e > > Gitweb: > > http://git.kernel.org/tip/f1e0bb0ad473a32d1b7e6d285ae9f7e47710bb5e > > Author: Yang Yingliang <yangyingli...@huawei.com> > > AuthorDate: Thu, 24 Sep 2015 17:32:13 +0800 > > Committer: Thomas Gleixner <t...@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 <yangyingli...@huawei.com> > > Acked-by: Russell King - ARM Linux <li...@arm.linux.org.uk> > > Cc: Jiang Liu <jiang....@linux.intel.com> > > Cc: Marc Zyngier <marc.zyng...@arm.com> > > Cc: Mark Rutland <mark.rutl...@arm.com> > > Cc: Will Deacon <will.dea...@arm.com> > > Cc: Hanjun Guo <hanjun....@linaro.org> > > Cc: <linux-arm-ker...@lists.infradead.org> > > Link: > > http://lkml.kernel.org/r/1443087135-17044-2-git-send-email-yangyingli...@huawei.com > > Signed-off-by: Thomas Gleixner <t...@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. I'll queue the corresponding arm64 patch for 4.4. -- Catalin -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/