Skip to contentSkip to conversation

regulator: rtq6752: make const read-only array fault_mask static

PATCH In review Colin Ian King 2 participants 2 messages Mar 17, 2025

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 regulator: rtq6752: make const read-only array fault_mask static

Don't populate the const read-only array fault_mask on the stack at run time, instead make it static.

---
 drivers/regulator/rtq6752-regulator.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/regulator/rtq6752-regulator.c +1 -1
index d35d844eff3b..618904ede72c 100644
@@ -105,7 +105,7 @@ static int rtq6752_get_error_flags(struct regulator_dev *rdev,
 				   unsigned int *flags)
 {
 	unsigned int val, events = 0;
-	const unsigned int fault_mask[] = {
+	static const unsigned int fault_mask[] = {
 		RTQ6752_PAVDDF_MASK, RTQ6752_NAVDDF_MASK };
 	int rid = rdev_get_id(rdev), ret;
 
Signature · 1 line
2.49.0
maintainer
#1 lore raw
Quoted 4 lines · Colin Ian King

Don't populate the const read-only array fault_mask on the stack at run time, instead make it static.

Applied to

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

Thanks!

[1/1] regulator: rtq6752: make const read-only array fault_mask static

      commit: 502d16c0bd8fa40ba194f00ccac4bc205a5c253f

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