summaryrefslogtreecommitdiff
path: root/arch/csky/kernel
diff options
context:
space:
mode:
authorGuo Ren <guoren@linux.alibaba.com>2020-01-07 12:21:25 +0800
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2020-03-12 13:00:16 +0100
commitc7ce725c525ad7dfa9d976a60776104cd8c5b4d3 (patch)
tree97dde8da1ccdd4725aed1a7780945e6260860763 /arch/csky/kernel
parenteb2ac8c497cddd2aa73e6f0777af486a859052ec (diff)
csky/smp: Fixup boot failed when CONFIG_SMP
[ Upstream commit c9492737b25ca32679ba3163609d938c9abfd508 ] If we use a non-ipi-support interrupt controller, it will cause panic here. We should let cpu up and work with CONFIG_SMP, when we use a non-ipi intc. Signed-off-by: Guo Ren <guoren@linux.alibaba.com> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'arch/csky/kernel')
-rw-r--r--arch/csky/kernel/smp.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/csky/kernel/smp.c b/arch/csky/kernel/smp.c
index b753d382e4ce..0bb0954d5570 100644
--- a/arch/csky/kernel/smp.c
+++ b/arch/csky/kernel/smp.c
@@ -120,7 +120,7 @@ void __init setup_smp_ipi(void)
int rc;
if (ipi_irq == 0)
- panic("%s IRQ mapping failed\n", __func__);
+ return;
rc = request_percpu_irq(ipi_irq, handle_ipi, "IPI Interrupt",
&ipi_dummy_dev);