[PATCH -next] ASoC: codecs: es8326: change es8326_regmap_config to static

[PATCH -next] ASoC: codecs: es8326: change es8326_regmap_config to static

[Yang Yingliang]

es8326_regmap_config is only used in es8326.c now, change it to static.

Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
---
 sound/soc/codecs/es8326.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sound/soc/codecs/es8326.c b/sound/soc/codecs/es8326.c
index 975302b2a61d..87c1cc16592b 100755
--- a/sound/soc/codecs/es8326.c
+++ b/sound/soc/codecs/es8326.c
@@ -207,7 +207,7 @@ static const struct regmap_access_table es8326_volatile_table = {
 	.n_yes_ranges = ARRAY_SIZE(es8326_volatile_ranges),
 };
 
-const struct regmap_config es8326_regmap_config = {
+static const struct regmap_config es8326_regmap_config = {
 	.reg_bits = 8,
 	.val_bits = 8,
 	.max_register = 0xff,
-- 
2.25.1

Re: [PATCH -next] ASoC: codecs: es8326: change es8326_regmap_config to static

[Mark Brown]

On Wed, 17 Aug 2022 17:15:19 +0800, Yang Yingliang wrote:
> es8326_regmap_config is only used in es8326.c now, change it to static.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: codecs: es8326: change es8326_regmap_config to static
      commit: 5c69f11ce85d4a8ea985a6d266574577e94c6506

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