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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 455A5ECAAA1 for ; Fri, 9 Sep 2022 18:01:00 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229818AbiIISA6 (ORCPT ); Fri, 9 Sep 2022 14:00:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58856 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229991AbiIISAY (ORCPT ); Fri, 9 Sep 2022 14:00:24 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CAAB55F994 for ; Fri, 9 Sep 2022 11:00:11 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 447A662047 for ; Fri, 9 Sep 2022 18:00:11 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 1A2B6C433C1; Fri, 9 Sep 2022 18:00:08 +0000 (UTC) Date: Fri, 9 Sep 2022 19:00:00 +0100 From: Catalin Marinas To: Qi Zheng Cc: Arnd Bergmann , kernel test robot , llvm@lists.linux.dev, kbuild-all@lists.01.org, Ammar Faizi , GNU/Weeb Mailing List , linux-kernel@vger.kernel.org Subject: Re: [ammarfaizi2-block:arm64/linux/for-next/misc 2/2] arch/arm64/kernel/irq.c:81:6: warning: no previous prototype for function 'do_softirq_own_stack' Message-ID: References: <202209091157.akimiv18-lkp@intel.com> <69409ea6-6daa-7973-c950-c6ca9ad96f50@bytedance.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <69409ea6-6daa-7973-c950-c6ca9ad96f50@bytedance.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Sep 09, 2022 at 03:07:36PM +0800, Qi Zheng wrote: > On 2022/9/9 14:30, Arnd Bergmann wrote: > > On Fri, Sep 9, 2022, at 5:12 AM, kernel test robot wrote: > > > tree: https://github.com/ammarfaizi2/linux-block > > > arm64/linux/for-next/misc > > > head: 2d2f3bb897a3de4190b1b6b296c3429d01327554 > > > commit: 2d2f3bb897a3de4190b1b6b296c3429d01327554 [2/2] arm64: run > > > softirqs on the per-CPU IRQ stack > > > config: arm64-randconfig-r023-20220907 > > > compiler: clang version 16.0.0 (https://github.com/llvm/llvm-project > > > 1546df49f5a6d09df78f569e4137ddb365a3e827) > > > reproduce (this is a W=1 build): > > > wget > > > https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross > > > -O ~/bin/make.cross > > > chmod +x ~/bin/make.cross > > > # install arm64 cross compiling tool for clang build > > > # apt-get install binutils-aarch64-linux-gnu > > > # > > > https://github.com/ammarfaizi2/linux-block/commit/2d2f3bb897a3de4190b1b6b296c3429d01327554 > > > git remote add ammarfaizi2-block > > > https://github.com/ammarfaizi2/linux-block > > > git fetch --no-tags ammarfaizi2-block arm64/linux/for-next/misc > > > git checkout 2d2f3bb897a3de4190b1b6b296c3429d01327554 > > > # save the config file > > > mkdir build_dir && cp config build_dir/.config > > > COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 > > > O=build_dir ARCH=arm64 SHELL=/bin/bash arch/arm64/kernel/ > > > > > > If you fix the issue, kindly add following tag where applicable > > > Reported-by: kernel test robot > > > > > > All warnings (new ones prefixed by >>): > > > > > > > > arch/arm64/kernel/irq.c:81:6: warning: no previous prototype for function 'do_softirq_own_stack' [-Wmissing-prototypes] > > > void do_softirq_own_stack(void) > > > ^ > > > arch/arm64/kernel/irq.c:81:1: note: declare 'static' if the function > > > is not intended to be used outside of this translation unit > > > void do_softirq_own_stack(void) > > > ^ > > > static > > > > > > I think we are missing an "#include " > > in arch/arm64/kernel/irq.c > > Indeed. Hi Catalin, do I need to resend the v4 version? Or can you help > me to apply the following code change to the for-next/misc directly? > Both are fine for me, depending on which way is convenient for you. :) I'll fold this in, that's the easiest. Thanks. -- Catalin