Hi, kernel test robot noticed the following build warnings: [auto build test WARNING on 78d4f34e2115b517bcbfe7ec0d018bbbb6f9b0b8] url: https://github.com/intel-lab-lkp/linux/commits/Mathieu-Dubois-Briand/dt-bindings-Add-MAX7360-MFD-device/20241220-002541 base: 78d4f34e2115b517bcbfe7ec0d018bbbb6f9b0b8 patch link: https://lore.kernel.org/r/20241219-mdb-max7360-support-v1-3-8e8317584121%40bootlin.com patch subject: [PATCH 3/8] mfd: Add max7360 support config: openrisc-randconfig-r122-20241220 (https://download.01.org/0day-ci/archive/20241221/202412210613.xoQvMKlk-lkp@xxxxxxxxx/config) compiler: or1k-linux-gcc (GCC) 14.2.0 reproduce: (https://download.01.org/0day-ci/archive/20241221/202412210613.xoQvMKlk-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/202412210613.xoQvMKlk-lkp@xxxxxxxxx/ sparse warnings: (new ones prefixed by >>) >> drivers/mfd/max7360.c:52:27: sparse: sparse: symbol 'max7360_volatile_ranges' was not declared. Should it be static? vim +/max7360_volatile_ranges +52 drivers/mfd/max7360.c 51 > 52 const struct regmap_range max7360_volatile_ranges[] = { 53 { 54 .range_min = MAX7360_REG_KEYFIFO, 55 .range_max = MAX7360_REG_KEYFIFO, 56 }, { 57 .range_min = 0x48, 58 .range_max = 0x4a, 59 }, 60 }; 61 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
