From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-9.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D3461C10F27 for ; Tue, 10 Mar 2020 13:31:18 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id AD07320675 for ; Tue, 10 Mar 2020 13:31:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1583847078; bh=F4Lhoeop5jyc/HLHpAGZSESF9WLzwH4clZlIidY28eo=; h=From:To:Cc:Subject:Date:In-Reply-To:References:List-ID:From; b=OZHabIH863cYo3LWiNy6sSor263lGzbQzg2DKmFu9RxprJnVEi2N94OBjlPihOyow ijRoZQoLchhA1PmiuQOAgWBLS+BsUWrksauRmU1r6UegSQru++SnRNGztB0nPU4lA5 Y2TJbGE4i/OBqSqeJBgfort3NeaKdBky8zukrKiM= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728459AbgCJNbN (ORCPT ); Tue, 10 Mar 2020 09:31:13 -0400 Received: from mail.kernel.org ([198.145.29.99]:54618 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728514AbgCJMuF (ORCPT ); Tue, 10 Mar 2020 08:50:05 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id F114720674; Tue, 10 Mar 2020 12:50:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1583844605; bh=F4Lhoeop5jyc/HLHpAGZSESF9WLzwH4clZlIidY28eo=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=mq/FmkkxqH62emZvc02uU+JWKH0BfqQBOgbubpaz+qmSpuGDIa2EwCaFZhFsPINka lTpWGAAX/0UwWm6Xul3O1fUvYdTn2+JtCgMv/3NQp6nXwTUTB4lcnIvd4gwX2uWN6I OvBAGVHjgR2KJi/3mLL4VnuRaAS+Fjd/DZCuYHpY= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Guo Ren , Sasha Levin Subject: [PATCH 5.4 052/168] csky/smp: Fixup boot failed when CONFIG_SMP Date: Tue, 10 Mar 2020 13:38:18 +0100 Message-Id: <20200310123640.610127709@linuxfoundation.org> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20200310123635.322799692@linuxfoundation.org> References: <20200310123635.322799692@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org From: Guo Ren [ 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 Signed-off-by: Sasha Levin --- arch/csky/kernel/smp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/csky/kernel/smp.c b/arch/csky/kernel/smp.c index b753d382e4cef..0bb0954d55709 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); -- 2.20.1