[PATCH v1 1/1] regulator: Reuse LINEAR_RANGE() in REGULATOR_LINEAR_RANGE()

[PATCH v1 1/1] regulator: Reuse LINEAR_RANGE() in REGULATOR_LINEAR_RANGE()

[Andy Shevchenko]

REGULATOR_LINEAR_RANGE() repeats what LINEAR_RANGE() provides.
Deduplicate the former by using the latter. No functional change
intended.

Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
 include/linux/regulator/driver.h | 7 +------
 1 file changed, 1 insertion(+), 6 deletions(-)

diff --git a/include/linux/regulator/driver.h b/include/linux/regulator/driver.h
index 4b7eceb3828b..22a07c0900a4 100644
--- a/include/linux/regulator/driver.h
+++ b/include/linux/regulator/driver.h
@@ -51,12 +51,7 @@ enum regulator_detection_severity {
 
 /* Initialize struct linear_range for regulators */
 #define REGULATOR_LINEAR_RANGE(_min_uV, _min_sel, _max_sel, _step_uV)	\
-{									\
-	.min		= _min_uV,					\
-	.min_sel	= _min_sel,					\
-	.max_sel	= _max_sel,					\
-	.step		= _step_uV,					\
-}
+	LINEAR_RANGE(_min_uV, _min_sel, _max_sel, _step_uV)
 
 /**
  * struct regulator_ops - regulator operations.
-- 
2.43.0.rc1.1.gbec44491f096

Re: [PATCH v1 1/1] regulator: Reuse LINEAR_RANGE() in REGULATOR_LINEAR_RANGE()

[Mark Brown]

On Tue, 19 Dec 2023 17:40:12 +0200, Andy Shevchenko wrote:
> REGULATOR_LINEAR_RANGE() repeats what LINEAR_RANGE() provides.
> Deduplicate the former by using the latter. No functional change
> intended.
> 
> 

Applied to

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

Thanks!

[1/1] regulator: Reuse LINEAR_RANGE() in REGULATOR_LINEAR_RANGE()
      commit: 67ba055dd7758c34f6e64c9d35132362c1e1f0b5

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