From: kernel test robot <lkp@intel.com>
To: chongjiapeng <jiapeng.chong@linux.alibaba.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org,
"Steven Rostedt (VMware)" <rostedt@goodmis.org>
Subject: kernel/trace/ftrace.c:7157:20: error: unused function 'ftrace_startup_enable'
Date: Sun, 13 Feb 2022 21:03:29 +0800 [thread overview]
Message-ID: <202202132037.4aN017dU-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: b81b1829e7e39f6cebdf6e4d5484eacbceda8554
commit: 172f7ba9772cae12f099fc563352e905dc9a1921 ftrace: Make ftrace_profile_pages_init static
date: 4 months ago
config: arm-randconfig-r001-20220213 (https://download.01.org/0day-ci/archive/20220213/202202132037.4aN017dU-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 478c237e21b2c3a83e46f26fcbeb3876682f9b14)
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 arm cross compiling tool for clang build
# apt-get install binutils-arm-linux-gnueabi
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=172f7ba9772cae12f099fc563352e905dc9a1921
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout 172f7ba9772cae12f099fc563352e905dc9a1921
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm SHELL=/bin/bash drivers/gpu/drm/ kernel/trace/
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 >>):
>> kernel/trace/ftrace.c:7157:20: error: unused function 'ftrace_startup_enable' [-Werror,-Wunused-function]
static inline void ftrace_startup_enable(int command) { }
^
1 error generated.
vim +/ftrace_startup_enable +7157 kernel/trace/ftrace.c
0b6e4d56bf7186 Frederic Weisbecker 2008-10-28 7155
8434dc9340cd2e Steven Rostedt (Red Hat 2015-01-20 7156) static inline int ftrace_init_dyn_tracefs(struct dentry *d_tracer) { return 0; }
df4fc31558dd2a Steven Rostedt 2008-11-26 @7157 static inline void ftrace_startup_enable(int command) { }
e1effa0144a1dd Steven Rostedt (Red Hat 2014-08-05 7158) static inline void ftrace_startup_all(int command) { }
8a56d7761d2d04 Steven Rostedt (Red Hat 2013-11-25 7159)
:::::: The code at line 7157 was first introduced by commit
:::::: df4fc31558dd2a3a30292ddb3a64c2a5befcec73 ftrace: add function tracing to single thread
:::::: TO: Steven Rostedt <srostedt@redhat.com>
:::::: CC: Ingo Molnar <mingo@elte.hu>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next reply other threads:[~2022-02-13 13:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-13 13:03 kernel test robot [this message]
2022-02-14 15:20 ` kernel/trace/ftrace.c:7157:20: error: unused function 'ftrace_startup_enable' Steven Rostedt
2022-02-14 15:53 ` Nathan Chancellor
2022-02-14 16:28 ` Masahiro Yamada
2022-02-14 17:00 ` Nathan Chancellor
2022-02-14 18:57 ` Steven Rostedt
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=202202132037.4aN017dU-lkp@intel.com \
--to=lkp@intel.com \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=rostedt@goodmis.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