regulator: hi6421: Use correct variable type for regmap api val argument
PATCH 1/1 regulator: hi6421: Use correct variable type for regmap api val argument
Use unsigned int instead of u32 for regmap_read/regmap_update_bits val argument.
--- drivers/regulator/hi6421-regulator.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
drivers/regulator/hi6421-regulator.c +4 -4
@@ -386,7 +386,7 @@ static int hi6421_regulator_enable(struct regulator_dev *rdev)static unsigned int hi6421_regulator_ldo_get_mode (struct regulator_dev *rdev) {struct hi6421_regulator_info *info =rdev_get_drvdata (rdev); -u32 reg_val; +unsigned int reg_val;regmap_read (rdev->regmap, rdev->desc->enable_reg, ®_val);if (reg_val & info->mode_mask)
@@ -398,7 +398,7 @@ static unsigned int hi6421_regulator_ldo_get_mode(struct regulator_dev *rdev)static unsigned int hi6421_regulator_buck_get_mode (struct regulator_dev *rdev) {struct hi6421_regulator_info *info =rdev_get_drvdata (rdev); -u32 reg_val; +unsigned int reg_val;regmap_read (rdev->regmap, rdev->desc->enable_reg, ®_val);if (reg_val & info->mode_mask)
@@ -411,7 +411,7 @@ static int hi6421_regulator_ldo_set_mode(struct regulator_dev *rdev, unsigned int mode) {struct hi6421_regulator_info *info =rdev_get_drvdata (rdev); -u32 new_mode; +unsigned int new_mode;switch (mode) {case REGULATOR_MODE_NORMAL :
@@ -435,7 +435,7 @@ static int hi6421_regulator_buck_set_mode(struct regulator_dev *rdev, unsigned int mode) {struct hi6421_regulator_info *info =rdev_get_drvdata (rdev); -u32 new_mode; +unsigned int new_mode;switch (mode) {case REGULATOR_MODE_NORMAL :
Signature · 1 line
2.25.1
Mark Brown
maintainerQuoted 2 lines · Axel Lin
Use unsigned int instead of u32 for regmap_read/regmap_update_bits val argument.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/1] regulator: hi6421: Use correct variable type for regmap api val argument
commit: ae60e6a9d24e89a74e2512204ad04de94921bdd2
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