The patch

   regulator: max77650: Use unsigned int for max77651_sbb1_regulator_volt_table

has been applied to the regulator tree at

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

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

>From 5fe0ed24379698feb3852950ae7579aa85993c24 Mon Sep 17 00:00:00 2001
From: Axel Lin <[email protected]>
Date: Wed, 6 Mar 2019 09:42:01 +0800
Subject: [PATCH] regulator: max77650: Use unsigned int for
 max77651_sbb1_regulator_volt_table

Make it consistent as .volt_table should be const unsigned int *.

Signed-off-by: Axel Lin <[email protected]>
Signed-off-by: Mark Brown <[email protected]>
---
 drivers/regulator/max77650-regulator.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/regulator/max77650-regulator.c 
b/drivers/regulator/max77650-regulator.c
index 31ebf34b01ec..5c4f86c98510 100644
--- a/drivers/regulator/max77650-regulator.c
+++ b/drivers/regulator/max77650-regulator.c
@@ -41,7 +41,7 @@ struct max77650_regulator_desc {
        unsigned int regB;
 };
 
-static const u32 max77651_sbb1_regulator_volt_table[] = {
+static const unsigned int max77651_sbb1_regulator_volt_table[] = {
        2400000, 3200000, 4000000, 4800000,
        2450000, 3250000, 4050000, 4850000,
        2500000, 3300000, 4100000, 4900000,
-- 
2.20.1

Reply via email to