From: kernel test robot <lkp@intel.com>
To: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
"Paul E. McKenney" <paulmck@kernel.org>
Subject: [paulmck-rcu:dev.2023.04.26a 35/51] arch/loongarch/kernel/process.c:68:1: warning: 'noreturn' function does return
Date: Thu, 27 Apr 2023 14:27:35 +0800 [thread overview]
Message-ID: <202304271412.cbmTIpbf-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2023.04.26a
head: 56b38a90a12f76e463a7381d8cff854926fa2b59
commit: 2b927bfdda366c1719e021cd0e9688baf933c9cf [35/51] objtool: Fix for unreachable instruction warning
config: loongarch-randconfig-r012-20230427 (https://download.01.org/0day-ci/archive/20230427/202304271412.cbmTIpbf-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 12.1.0
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
# https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git/commit/?id=2b927bfdda366c1719e021cd0e9688baf933c9cf
git remote add paulmck-rcu https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
git fetch --no-tags paulmck-rcu dev.2023.04.26a
git checkout 2b927bfdda366c1719e021cd0e9688baf933c9cf
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=loongarch olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=loongarch SHELL=/bin/bash arch/loongarch/kernel/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202304271412.cbmTIpbf-lkp@intel.com/
All warnings (new ones prefixed by >>):
arch/loongarch/kernel/process.c:109:5: warning: no previous prototype for 'arch_dup_task_struct' [-Wmissing-prototypes]
109 | int arch_dup_task_struct(struct task_struct *dst, struct task_struct *src)
| ^~~~~~~~~~~~~~~~~~~~
arch/loongarch/kernel/process.c:301:15: warning: no previous prototype for 'arch_align_stack' [-Wmissing-prototypes]
301 | unsigned long arch_align_stack(unsigned long sp)
| ^~~~~~~~~~~~~~~~
arch/loongarch/kernel/process.c: In function 'arch_cpu_idle_dead':
>> arch/loongarch/kernel/process.c:68:1: warning: 'noreturn' function does return
68 | }
| ^
vim +/noreturn +68 arch/loongarch/kernel/process.c
803b0fc5c3f2ba Huacai Chen 2022-05-31 63
46859ac8af52ae Huacai Chen 2022-05-31 64 #ifdef CONFIG_HOTPLUG_CPU
46859ac8af52ae Huacai Chen 2022-05-31 65 void arch_cpu_idle_dead(void)
46859ac8af52ae Huacai Chen 2022-05-31 66 {
46859ac8af52ae Huacai Chen 2022-05-31 67 play_dead();
46859ac8af52ae Huacai Chen 2022-05-31 @68 }
46859ac8af52ae Huacai Chen 2022-05-31 69 #endif
46859ac8af52ae Huacai Chen 2022-05-31 70
:::::: The code at line 68 was first introduced by commit
:::::: 46859ac8af52ae599e1b51992ddef3eb43f295fc LoongArch: Add multi-processor (SMP) support
:::::: TO: Huacai Chen <chenhuacai@loongson.cn>
:::::: CC: Huacai Chen <chenhuacai@loongson.cn>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-04-27 6:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202304271412.cbmTIpbf-lkp@intel.com \
--to=lkp@intel.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paulmck@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.