summaryrefslogtreecommitdiff
path: root/Documentation/devicetree/bindings/regulator
diff options
context:
space:
mode:
authorMark Brown <broonie@kernel.org>2021-07-12 11:30:35 +0100
committerMark Brown <broonie@kernel.org>2021-07-12 11:30:35 +0100
commit9705c49c3b5e8640fa1afd24f93a391ac0f793a4 (patch)
tree88f8c06e1892366621b927d338620defa49f0b47 /Documentation/devicetree/bindings/regulator
parent2c8dad1ea815f1a2003f501d9f71b9d9961f2f3a (diff)
parent4d9f4d1de3ceb84fa6ce68177a26b8fac6a71290 (diff)
Merge series "regulator: devres: remove unused device-managed unregister APIs" from Alexandru Ardelean <aardelean@deviqon.com>:
These APIs aren't used anywhere and most-likely exist because of the general principle of C APIs, where if an API function does an allocation/registration, it must also have an equivalent deallocation/deregistration counterpart. For devm_ functions this isn't all that true (for all cases), as the idea of these function is to provide an auto-cleanup logic on drivers/system de-init. Removing these discourages any weird logic that could be created with such an API functions. Alexandru Ardelean (4): regulator: devres: remove devm_regulator_unregister_notifier() function regulator: devres: remove devm_regulator_unregister() function regulator: devres: remove devm_regulator_bulk_unregister_supply_alias() regulator: devres: unexport devm_regulator_unregister_supply_alias() drivers/regulator/devres.c | 105 +---------------------------- include/linux/regulator/consumer.h | 23 ------- include/linux/regulator/driver.h | 1 - 3 files changed, 2 insertions(+), 127 deletions(-) -- 2.31.1
Diffstat (limited to 'Documentation/devicetree/bindings/regulator')
0 files changed, 0 insertions, 0 deletions