Re: [PATCH v2 bpf-next 1/2] cpuidle: Implement BPF extensible cpuidle governor class

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Lin,

kernel test robot noticed the following build warnings:

[auto build test WARNING on bpf-next/master]

url:    https://github.com/intel-lab-lkp/linux/commits/Lin-Yikai/cpuidle-Implement-BPF-extensible-cpuidle-governor-class/20250901-220011
base:   https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
patch link:    https://lore.kernel.org/r/20250901135609.76590-2-yikai.lin%40vivo.com
patch subject: [PATCH v2 bpf-next 1/2] cpuidle: Implement BPF extensible cpuidle governor class
config: arm-randconfig-r131-20250907 (https://download.01.org/0day-ci/archive/20250907/202509071459.Gkqhd7YV-lkp@xxxxxxxxx/config)
compiler: arm-linux-gnueabi-gcc (GCC) 8.5.0
reproduce: (https://download.01.org/0day-ci/archive/20250907/202509071459.Gkqhd7YV-lkp@xxxxxxxxx/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@xxxxxxxxx>
| Closes: https://lore.kernel.org/oe-kbuild-all/202509071459.Gkqhd7YV-lkp@xxxxxxxxx/

sparse warnings: (new ones prefixed by >>)
>> drivers/cpuidle/governors/ext.c:141:1: sparse: sparse: symbol 'ops_enabled_key' was not declared. Should it be static?

vim +/ops_enabled_key +141 drivers/cpuidle/governors/ext.c

   139	
   140	static DEFINE_MUTEX(ops_mutex);
 > 141	DEFINE_STATIC_KEY_FALSE(ops_enabled_key);
   142	static atomic_t ops_enable_state_var = ATOMIC_INIT(OPS_DISABLED);
   143	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki




[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux