From: kernel test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
linux-kernel@vger.kernel.org
Subject: [rcu:rcu/next 10/11] kernel/rcu/tasks.h:594:20: error: static declaration of 'exit_tasks_rcu_start' follows non-static declaration
Date: Fri, 28 Aug 2020 03:45:13 +0800 [thread overview]
Message-ID: <202008280306.rWMY2XnY%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2652 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/next
head: 2ec296bd21c79b080bd6b3fb143122f18440d930
commit: 8c8942d72e9bf1e19b6af0a8df4c7f44d2d384c0 [10/11] rcu-tasks: Prevent complaints of unused show_rcu_tasks_classic_gp_kthread()
config: x86_64-randconfig-a014-20200827 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project 71f3169e1baeff262583b35ef88f8fb6df7be85e)
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 x86_64 cross compiling tool for clang build
# apt-get install binutils-x86-64-linux-gnu
git checkout 8c8942d72e9bf1e19b6af0a8df4c7f44d2d384c0
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from kernel/rcu/update.c:578:
>> kernel/rcu/tasks.h:594:20: error: static declaration of 'exit_tasks_rcu_start' follows non-static declaration
static inline void exit_tasks_rcu_start(void) { }
^
include/linux/rcupdate.h:181:6: note: previous declaration is here
void exit_tasks_rcu_start(void);
^
In file included from kernel/rcu/update.c:578:
>> kernel/rcu/tasks.h:595:20: error: static declaration of 'exit_tasks_rcu_finish' follows non-static declaration
static inline void exit_tasks_rcu_finish(void) { exit_tasks_rcu_finish_trace(current); }
^
include/linux/rcupdate.h:182:6: note: previous declaration is here
void exit_tasks_rcu_finish(void);
^
2 errors generated.
# https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git/commit/?id=8c8942d72e9bf1e19b6af0a8df4c7f44d2d384c0
git remote add rcu https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
git fetch --no-tags rcu rcu/next
git checkout 8c8942d72e9bf1e19b6af0a8df4c7f44d2d384c0
vim +/exit_tasks_rcu_start +594 kernel/rcu/tasks.h
591
592 #else /* #ifdef CONFIG_TASKS_RCU */
593 static inline void show_rcu_tasks_classic_gp_kthread(void) { }
> 594 static inline void exit_tasks_rcu_start(void) { }
> 595 static inline void exit_tasks_rcu_finish(void) { exit_tasks_rcu_finish_trace(current); }
596 #endif /* #else #ifdef CONFIG_TASKS_RCU */
597
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 31526 bytes --]
next reply other threads:[~2020-08-27 19:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 19:45 kernel test robot [this message]
2020-08-27 22:36 ` Paul E. McKenney
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=202008280306.rWMY2XnY%lkp@intel.com \
--to=lkp@intel.com \
--cc=clang-built-linux@googlegroups.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®