aboutsummaryrefslogtreecommitdiffstats
path: root/include/linux/regulator
diff options
context:
space:
mode:
authorJavier Martinez Canillas <javier@osg.samsung.com>2016-03-17 14:54:54 -0300
committerMark Brown <broonie@kernel.org>2016-03-28 19:39:17 +0100
commit86cf635a316e89ba6ae79f452cedb5acddccf570 (patch)
tree74dd39d51e96abe81fd6495f9059b9ee5a4a1930 /include/linux/regulator
parentLinux 4.6-rc1 (diff)
downloadlinux-dev-86cf635a316e89ba6ae79f452cedb5acddccf570.tar.xz
linux-dev-86cf635a316e89ba6ae79f452cedb5acddccf570.zip
regulator: Rename files for Maxim PMIC drivers
Most Maxim PMIC regulator drivers are for sub-devices of Multi-Function Devices with drivers under drivers/mfd. But for many of these, the same object file name was used for both the MFD and the regulator drivers. Having 2 different drivers with the same name causes a lot of confusion to Kbuild, specially if these are built as module since only one module will be installed and also exported symbols will be undefined due being overwritten by the other module during modpost. For example, it fixes the following issue when both drivers are module: $ make M=drivers/regulator/ ... CC [M] drivers/regulator//max14577.o Building modules, stage 2. MODPOST 1 modules WARNING: "maxim_charger_calc_reg_current" [drivers/regulator//max14577.ko] undefined! WARNING: "maxim_charger_currents" [drivers/regulator//max14577.ko] undefined! Reported-by: Chanwoo Choi <cw00.choi@samsung.com> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com> Reviewed-by: Chanwoo Choi <cw00.choi@samsung.com> Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'include/linux/regulator')
0 files changed, 0 insertions, 0 deletions