From: kernel test robot <lkp@intel.com>
To: Heiko Stuebner <heiko@sntech.de>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org, Guo Ren <guoren@linux.alibaba.com>
Subject: [csky-linux:riscv_compat_v6_svpbmt-v6 10/35] arch/riscv/kernel/cpufeature.c:185:6: warning: variable 'cpu_apply_feature' set but not used
Date: Fri, 11 Feb 2022 02:13:49 +0800 [thread overview]
Message-ID: <202202110204.3m29JCRv-lkp@intel.com> (raw)
tree: https://github.com/c-sky/csky-linux riscv_compat_v6_svpbmt-v6
head: 54acb36c958fc990cc59889f79c8ddca7386c295
commit: 9a8cf89570e893738c501551591b03bd868c825c [10/35] riscv: add cpufeature handling via alternatives
config: riscv-randconfig-r042-20220208 (https://download.01.org/0day-ci/archive/20220211/202202110204.3m29JCRv-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project aa845d7a245d85c441d0bd44fc7b6c3be8f3de8d)
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 riscv cross compiling tool for clang build
# apt-get install binutils-riscv64-linux-gnu
# https://github.com/c-sky/csky-linux/commit/9a8cf89570e893738c501551591b03bd868c825c
git remote add csky-linux https://github.com/c-sky/csky-linux
git fetch --no-tags csky-linux riscv_compat_v6_svpbmt-v6
git checkout 9a8cf89570e893738c501551591b03bd868c825c
# 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=riscv SHELL=/bin/bash arch/riscv/kernel/ arch/riscv/mm/ drivers/base/firmware_loader/ drivers/pci/ drivers/target/ fs/erofs/ fs/pstore/ kernel/ mm/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> arch/riscv/kernel/cpufeature.c:185:6: warning: variable 'cpu_apply_feature' set but not used [-Wunused-but-set-variable]
u32 cpu_apply_feature = 0;
^
1 warning generated.
vim +/cpu_apply_feature +185 arch/riscv/kernel/cpufeature.c
180
181 void riscv_cpufeature_patch_func(struct alt_entry *begin, struct alt_entry *end,
182 unsigned int stage)
183 {
184 u32 cpu_req_feature = cpufeature_probe(stage);
> 185 u32 cpu_apply_feature = 0;
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [csky-linux:riscv_compat_v6_svpbmt-v6 10/35] arch/riscv/kernel/cpufeature.c:185:6: warning: variable 'cpu_apply_feature' set but not used
Date: Fri, 11 Feb 2022 02:13:49 +0800 [thread overview]
Message-ID: <202202110204.3m29JCRv-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2159 bytes --]
tree: https://github.com/c-sky/csky-linux riscv_compat_v6_svpbmt-v6
head: 54acb36c958fc990cc59889f79c8ddca7386c295
commit: 9a8cf89570e893738c501551591b03bd868c825c [10/35] riscv: add cpufeature handling via alternatives
config: riscv-randconfig-r042-20220208 (https://download.01.org/0day-ci/archive/20220211/202202110204.3m29JCRv-lkp(a)intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project aa845d7a245d85c441d0bd44fc7b6c3be8f3de8d)
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 riscv cross compiling tool for clang build
# apt-get install binutils-riscv64-linux-gnu
# https://github.com/c-sky/csky-linux/commit/9a8cf89570e893738c501551591b03bd868c825c
git remote add csky-linux https://github.com/c-sky/csky-linux
git fetch --no-tags csky-linux riscv_compat_v6_svpbmt-v6
git checkout 9a8cf89570e893738c501551591b03bd868c825c
# 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=riscv SHELL=/bin/bash arch/riscv/kernel/ arch/riscv/mm/ drivers/base/firmware_loader/ drivers/pci/ drivers/target/ fs/erofs/ fs/pstore/ kernel/ mm/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> arch/riscv/kernel/cpufeature.c:185:6: warning: variable 'cpu_apply_feature' set but not used [-Wunused-but-set-variable]
u32 cpu_apply_feature = 0;
^
1 warning generated.
vim +/cpu_apply_feature +185 arch/riscv/kernel/cpufeature.c
180
181 void riscv_cpufeature_patch_func(struct alt_entry *begin, struct alt_entry *end,
182 unsigned int stage)
183 {
184 u32 cpu_req_feature = cpufeature_probe(stage);
> 185 u32 cpu_apply_feature = 0;
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
next reply other threads:[~2022-02-10 18:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 18:13 kernel test robot [this message]
2022-02-10 18:13 ` [csky-linux:riscv_compat_v6_svpbmt-v6 10/35] arch/riscv/kernel/cpufeature.c:185:6: warning: variable 'cpu_apply_feature' set but not used kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2022-02-10 18:03 kernel test robot
2022-02-10 18:03 ` kernel test robot
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=202202110204.3m29JCRv-lkp@intel.com \
--to=lkp@intel.com \
--cc=guoren@linux.alibaba.com \
--cc=heiko@sntech.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
/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.