The volatile_reg function is named as tps6287x_volatile_reg by mistake
when enabing the REGCACHE_MAPLE support.

Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
---
 drivers/regulator/tps6286x-regulator.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/regulator/tps6286x-regulator.c b/drivers/regulator/tps6286x-regulator.c
index 778f169b0acc..e29aab06bf79 100644
--- a/drivers/regulator/tps6286x-regulator.c
+++ b/drivers/regulator/tps6286x-regulator.c
@@ -25,7 +25,7 @@
 #define TPS6286X_MAX_MV		1675
 #define TPS6286X_STEP_MV	5
 
-static bool tps6287x_volatile_reg(struct device *dev, unsigned int reg)
+static bool tps6286x_volatile_reg(struct device *dev, unsigned int reg)
 {
 	return reg == TPS6286X_STATUS;
 }
@@ -34,7 +34,7 @@ static const struct regmap_config tps6286x_regmap_config = {
 	.reg_bits = 8,
 	.val_bits = 8,
 	.cache_type = REGCACHE_MAPLE,
-	.volatile_reg = tps6287x_volatile_reg,
+	.volatile_reg = tps6286x_volatile_reg,
 };
 
 static int tps6286x_set_mode(struct regulator_dev *rdev, unsigned int mode)
-- 
2.50.0

On Mon, 14 Jul 2025 09:04:56 +0800, Jisheng Zhang wrote:
> The volatile_reg function is named as tps6287x_volatile_reg by mistake
> when enabing the REGCACHE_MAPLE support.
> 
> 

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/1] regulator: tps6286x-regulator: Fix a copy & paste error
      commit: 43728a6434f9eca0385fd180d8452a5071678a5b

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark