From: kernel test robot <lkp@intel.com>
To: Charlie Jenkins <charlie@rivosinc.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Palmer Dabbelt <palmer@rivosinc.com>,
Conor Dooley <conor.dooley@microchip.com>,
Andy Chiu <andy.chiu@sifive.com>,
Yu Chien Peter Lin <peterlin@andestech.com>
Subject: [linux-next:master 13398/13762] arch/riscv/kernel/vendor_extensions/andes.c:11:33: sparse: sparse: symbol 'riscv_isa_vendor_ext_andes' was not declared. Should it be static?
Date: Wed, 24 Jul 2024 15:13:18 +0800 [thread overview]
Message-ID: <202407241530.ej5SVgX1-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 9ec6ec93f2c1e6cd2911e2a4acd5ac85e13bb3e2
commit: 23c996fc2bc1978a02c64eddb90b4ab5d309c8df [13398/13762] riscv: Extend cpufeature.c to detect vendor extensions
config: riscv-randconfig-r123-20240724 (https://download.01.org/0day-ci/archive/20240724/202407241530.ej5SVgX1-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 14.1.0
reproduce: (https://download.01.org/0day-ci/archive/20240724/202407241530.ej5SVgX1-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202407241530.ej5SVgX1-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> arch/riscv/kernel/vendor_extensions/andes.c:11:33: sparse: sparse: symbol 'riscv_isa_vendor_ext_andes' was not declared. Should it be static?
vim +/riscv_isa_vendor_ext_andes +11 arch/riscv/kernel/vendor_extensions/andes.c
9
10 /* All Andes vendor extensions supported in Linux */
> 11 const struct riscv_isa_ext_data riscv_isa_vendor_ext_andes[] = {
12 __RISCV_ISA_EXT_DATA(xandespmu, RISCV_ISA_VENDOR_EXT_XANDESPMU),
13 };
14
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-07-24 7:14 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=202407241530.ej5SVgX1-lkp@intel.com \
--to=lkp@intel.com \
--cc=andy.chiu@sifive.com \
--cc=charlie@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=palmer@rivosinc.com \
--cc=peterlin@andestech.com \
/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