From: kernel test robot <lkp@intel.com>
To: Jad Keskes <inasj268@gmail.com>, Mark Brown <broonie@kernel.org>,
Chanwoo Choi <cw00.choi@samsung.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>, Lee Jones <lee@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Jad Keskes <inasj268@gmail.com>
Subject: Re: [PATCH v3] regulator: max14577: fix set_mode clobbering enable on MAX77836 LDOs
Date: Wed, 17 Jun 2026 08:38:51 +0800 [thread overview]
Message-ID: <202606170800.s4CQUJ3m-lkp@intel.com> (raw)
In-Reply-To: <20260616170256.1659595-1-inasj268@gmail.com>
Hi Jad,
kernel test robot noticed the following build errors:
[auto build test ERROR on broonie-regulator/for-next]
[also build test ERROR on lee-mfd/for-mfd-next lee-leds/for-leds-next lee-mfd/for-mfd-fixes linus/master v7.1 next-20260616]
[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/Jad-Keskes/regulator-max14577-fix-set_mode-clobbering-enable-on-MAX77836-LDOs/20260617-024714
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
patch link: https://lore.kernel.org/r/20260616170256.1659595-1-inasj268%40gmail.com
patch subject: [PATCH v3] regulator: max14577: fix set_mode clobbering enable on MAX77836 LDOs
config: parisc-randconfig-r073-20260617 (https://download.01.org/0day-ci/archive/20260617/202606170800.s4CQUJ3m-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 16.1.0
smatch: v0.5.0-9185-gbcc58b9c
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260617/202606170800.s4CQUJ3m-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/202606170800.s4CQUJ3m-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/regulator/max14577-regulator.c:208:10: error: 'const struct regulator_ops' has no member named 'of_map_mode'
208 | .of_map_mode = max77836_ldo_of_map_mode,
| ^~~~~~~~~~~
>> drivers/regulator/max14577-regulator.c:208:35: error: initialization of 'unsigned int (*)(struct regulator_dev *)' from incompatible pointer type 'unsigned int (*)(unsigned int)' [-Wincompatible-pointer-types]
208 | .of_map_mode = max77836_ldo_of_map_mode,
| ^~~~~~~~~~~~~~~~~~~~~~~~
drivers/regulator/max14577-regulator.c:208:35: note: (near initialization for 'max77836_ldo_ops.get_mode')
drivers/regulator/max14577-regulator.c:187:21: note: 'max77836_ldo_of_map_mode' declared here
187 | static unsigned int max77836_ldo_of_map_mode(unsigned int mode)
| ^~~~~~~~~~~~~~~~~~~~~~~~
drivers/regulator/max14577-regulator.c:208:35: warning: initialized field overwritten [-Woverride-init]
208 | .of_map_mode = max77836_ldo_of_map_mode,
| ^~~~~~~~~~~~~~~~~~~~~~~~
drivers/regulator/max14577-regulator.c:208:35: note: (near initialization for 'max77836_ldo_ops.get_mode')
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for MFD_STMFX
Depends on [n]: HAS_IOMEM [=y] && I2C [=y] && OF [=n]
Selected by [m]:
- PINCTRL_STMFX [=m] && PINCTRL [=y] && I2C [=y] && HAS_IOMEM [=y]
vim +208 drivers/regulator/max14577-regulator.c
197
198 static const struct regulator_ops max77836_ldo_ops = {
199 .is_enabled = regulator_is_enabled_regmap,
200 .enable = max77836_ldo_enable,
201 .disable = max77836_ldo_disable,
202 .list_voltage = regulator_list_voltage_linear,
203 .map_voltage = regulator_map_voltage_linear,
204 .get_voltage_sel = regulator_get_voltage_sel_regmap,
205 .set_voltage_sel = regulator_set_voltage_sel_regmap,
206 .get_mode = max77836_ldo_get_mode,
207 .set_mode = max77836_ldo_set_mode,
> 208 .of_map_mode = max77836_ldo_of_map_mode,
209 };
210
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-06-17 0:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 17:02 Jad Keskes
2026-06-17 0:18 ` kernel test robot
2026-06-17 0:38 ` kernel test robot [this message]
2026-06-17 6:59 ` Lee Jones
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=202606170800.s4CQUJ3m-lkp@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=inasj268@gmail.com \
--cc=krzk@kernel.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®