Skip to contentSkip to conversation

ASoC: rt1320: fix size_t format string

PATCH In review Arnd Bergmann 2 participants 2 messages Dec 23, 2025 – Dec 24, 2025

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

PATCH 1/1 ASoC: rt1320: fix size_t format string

From: Arnd Bergmann <[email protected]>

Printing a size_t portably requires the use of %z instead of %l:

sound/soc/codecs/rt1320-sdw.c:1494:30: error: format '%lx' expects argument of type 'long unsigned int', but argument 5 has type 'size_t' {aka 'unsigned int'} [-Werror=format=]

 1494 |                 dev_dbg(dev, "%s, rae_fw size=0x%lx\n", __func__, rae_fw->size);
      |                              ^~~~~~~~~~~~~~~~~~~~~~~~~
Fixes 22937af75abb ("ASoC: rt1320: support RAE parameters loading")
---
 sound/soc/codecs/rt1320-sdw.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
sound/soc/codecs/rt1320-sdw.c +1 -1
index 2999ab95971a..245b9d9980f9 100644
@@ -1491,7 +1491,7 @@ static int rt1320_rae_load(struct rt1320_sdw_priv *rt1320)
 			return -ETIMEDOUT;
 		}
 
-		dev_dbg(dev, "%s, rae_fw size=0x%lx\n", __func__, rae_fw->size);
+		dev_dbg(dev, "%s, rae_fw size=0x%zx\n", __func__, rae_fw->size);
 		regcache_cache_bypass(rt1320->regmap, true);
 		for (fw_offset = 0; fw_offset < rae_fw->size;) {
 
Signature · 1 line
2.39.5
maintainer
#1 lore raw
Quoted 8 lines · Arnd Bergmann

Printing a size_t portably requires the use of %z instead of %l:

sound/soc/codecs/rt1320-sdw.c:1494:30: error: format '%lx' expects argument of type 'long unsigned int', but argument 5 has type 'size_t' {aka 'unsigned int'} [-Werror=format=]

 1494 |                 dev_dbg(dev, "%s, rae_fw size=0x%lx\n", __func__, rae_fw->size);
      |                              ^~~~~~~~~~~~~~~~~~~~~~~~~

[...]

Applied to

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

Thanks!

[1/1] ASoC: rt1320: fix size_t format string

      commit: 284853affe73fe1ca9786bd52b934eb9d420a942

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