2021-07-15 14:21:23

by Colin King

[permalink] [raw]
Subject: [PATCH] regulator: rt6245: make a const array func_base static, makes object smaller

From: Colin Ian King <[email protected]>

Don't populate the const array func_base on the stack but instead it
static. Makes the object code smaller by 55 bytes:

Before:
text data bss dec hex filename
6422 3216 64 9702 25e6 drivers/regulator/rt6245-regulator.o

After:
text data bss dec hex filename
6303 3280 64 9647 25af drivers/regulator/rt6245-regulator.o

Reduction of 55 bytes

(gcc version 10.3.0)

Signed-off-by: Colin Ian King <[email protected]>
---
drivers/regulator/rt6245-regulator.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/regulator/rt6245-regulator.c b/drivers/regulator/rt6245-regulator.c
index d3299a72fd10..cb22a207e9ff 100644
--- a/drivers/regulator/rt6245-regulator.c
+++ b/drivers/regulator/rt6245-regulator.c
@@ -144,7 +144,7 @@ static int rt6245_init_device_properties(struct device *dev)
static int rt6245_reg_write(void *context, unsigned int reg, unsigned int val)
{
struct i2c_client *i2c = context;
- const u8 func_base[] = { 0x6F, 0x73, 0x78, 0x61, 0x7C, 0 };
+ static const u8 func_base[] = { 0x6F, 0x73, 0x78, 0x61, 0x7C, 0 };
unsigned int code, bit_count;

code = func_base[reg];
--
2.31.1


2021-07-15 19:59:25

by Mark Brown

[permalink] [raw]
Subject: Re: [PATCH] regulator: rt6245: make a const array func_base static, makes object smaller

On Thu, 15 Jul 2021 15:15:31 +0100, Colin King wrote:
> Don't populate the const array func_base on the stack but instead it
> static. Makes the object code smaller by 55 bytes:
>
> Before:
> text data bss dec hex filename
> 6422 3216 64 9702 25e6 drivers/regulator/rt6245-regulator.o
>
> [...]

Applied to

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

Thanks!

[1/1] regulator: rt6245: make a const array func_base static, makes object smaller
commit: 508f8ccd993d1ff5c9a3092f179f33bd7a825bac

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