linux-kernel - Re: [PATCH 2/3] regulator: max77675: Add MAX77675 regulator driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <202509271318.cU4bEADk-lkp@intel.com>
Date: Sat, 27 Sep 2025 13:30:40 +0800
From: kernel test robot <lkp@...el.com>
To: Joan-Na-adi <joan.na.devcode@...il.com>,
	Liam Girdwood <lgirdwood@...il.com>
Cc: oe-kbuild-all@...ts.linux.dev, Mark Brown <broonie@...nel.org>,
	Rob Herring <robh@...nel.org>,
	Krzysztof Kozlowski <krzk@...nel.org>,
	Conor Dooley <conor+dt@...nel.org>, linux-kernel@...r.kernel.org,
	devicetree@...r.kernel.org, Joan Na <joan.na@...log.com>
Subject: Re: [PATCH 2/3] regulator: max77675: Add MAX77675 regulator driver

Hi Joan-Na-adi,

kernel test robot noticed the following build warnings:

[auto build test WARNING on broonie-regulator/for-next]
[also build test WARNING on robh/for-next linus/master v6.17-rc7 next-20250926]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Joan-Na-adi/dt-bindings-regulator-Add-MAX77675-binding-header/20250926-134116
base:   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
patch link:    https://lore.kernel.org/r/20250926053757.480086-3-joan.na%40analog.com
patch subject: [PATCH 2/3] regulator: max77675: Add MAX77675 regulator driver
config: parisc-randconfig-r122-20250927 (https://download.01.org/0day-ci/archive/20250927/202509271318.cU4bEADk-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 10.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250927/202509271318.cU4bEADk-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@...el.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202509271318.cU4bEADk-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/regulator/max77675-regulator.c:367:10: sparse: sparse: Initializer entry defined twice
   drivers/regulator/max77675-regulator.c:371:10: sparse:   also defined here

vim +367 drivers/regulator/max77675-regulator.c

   365	
   366	static const struct regulator_ops max77675_regulator_ops = {
 > 367		.list_voltage         = regulator_list_voltage_linear,
   368		.enable               = regulator_enable_regmap,
   369		.disable              = regulator_disable_regmap,
   370		.is_enabled           = regulator_is_enabled_regmap,
   371		.list_voltage         = regulator_list_voltage_linear,
   372		.map_voltage          = regulator_map_voltage_linear,
   373		.set_voltage_sel      = regulator_set_voltage_sel_regmap,
   374		.get_voltage_sel      = regulator_get_voltage_sel_regmap,
   375		.set_active_discharge = regulator_set_active_discharge_regmap,
   376		.get_error_flags      = max77675_get_error_flags,
   377	};
   378	

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