Mauro Carvalho Chehab bd3ebed930 regulator: driver.h: fix regulator_map_* function names ... The toolchain produces a warning on this driver when building the docs: ./include/linux/regulator/driver.h:284: WARNING: Unknown target name: "regulator_regmap_x_voltage". While fixing it, we notices that there's no function names with the above pattern. It seems that some previous patch renamed it to regulator_map_* instead. So, change the function name, replacing "x" by "*", with is a more used way to add a wildcard, and escape those with ``literal`` markup, in order to avoid the toolchain to think that this is a link to some existing document chapter. Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org> Link: https://lore.kernel.org/r/b9f5687bcf981a88c9d1fd04d759a540fda53a99.1584456635.git.mchehab+huawei@kernel.org Signed-off-by: Mark Brown <broonie@kernel.org>		2020-03-18 21:57:20 +00:00
..
ab8500.h	regulator: ab8500: Remove SYSCLKREQ from enum ab8505_regulator_id	2019-11-07 13:10:08 +00:00
act8865.h
arizona-ldo1.h
arizona-micsupp.h
consumer.h	regulator fix for "regulator: core: Add regulator_is_equal() helper"	2020-01-15 14:10:45 +00:00
coupler.h	regulator: core: Expose some of core functions needed by couplers	2019-06-25 12:15:35 +01:00
da9211.h
db8500-prcmu.h
driver.h	regulator: driver.h: fix regulator_map_* function names	2020-03-18 21:57:20 +00:00
fan53555.h
fixed.h	regulator: fixed: add off-on-delay	2019-10-29 12:32:12 +00:00
gpio-regulator.h
lp872x.h
lp3971.h
lp3972.h
machine.h	Merge remote-tracking branch 'regulator/topic/coupled' into regulator-next	2019-07-04 17:34:34 +01:00
max1586.h
max8649.h
max8660.h
max8952.h
max8973-regulator.h
mt6311.h
mt6323-regulator.h
mt6358-regulator.h	regulator: mt6358: Add support for MT6358 regulator	2019-08-28 11:51:27 +01:00
mt6380-regulator.h
mt6397-regulator.h
of_regulator.h
pfuze100.h
tps6507x.h
tps51632-regulator.h
tps62360.h
userspace-consumer.h