Skip to contentSkip to conversation

ASoC: cs35l56: Include array_size.h

PATCH In review Richard Fitzgerald 2 participants 2 messages Apr 10, 2024

Subsystems (3)
lore
Share & tools
lore

Richard Fitzgerald

author maintainer
#0 lore raw

PATCH 1/1 ASoC: cs35l56: Include array_size.h

Explicitly #include array_size.h for the source files that use ARRAY_SIZE().

---
 sound/soc/codecs/cs35l56-shared.c | 1 +
 sound/soc/codecs/cs35l56.c        | 1 +
 2 files changed, 2 insertions(+)
sound/soc/codecs/cs35l56-shared.c +1 -0
index ec1d95e57061..3aa39f5923eb 100644
@@ -5,6 +5,7 @@
 // Copyright (C) 2023 Cirrus Logic, Inc. and
 //                    Cirrus Logic International Semiconductor Ltd.
 
+#include <linux/array_size.h>
 #include <linux/firmware/cirrus/wmfw.h>
 #include <linux/gpio/consumer.h>
 #include <linux/regmap.h>
sound/soc/codecs/cs35l56.c +1 -0
index 6331b8c6136e..dfd703d9e12f 100644
@@ -6,6 +6,7 @@
 //                    Cirrus Logic International Semiconductor Ltd.
 
 #include <linux/acpi.h>
+#include <linux/array_size.h>
 #include <linux/completion.h>
 #include <linux/debugfs.h>
 #include <linux/delay.h>
Signature · 1 line
2.39.2
maintainer
#1 lore raw
Quoted 4 lines · Richard Fitzgerald

Explicitly #include array_size.h for the source files that use ARRAY_SIZE().

Applied to

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

Thanks!

[1/1] ASoC: cs35l56: Include array_size.h

      commit: 28d31ffac3d3ef6d60c4eb392a47d5e19dbb15e8

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