[PATCH] ASoC: rt1320: fix size_t format string

[PATCH] ASoC: rt1320: fix size_t format string

[Arnd Bergmann]

From: Arnd Bergmann <arnd@arndb.de>

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")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
---
 sound/soc/codecs/rt1320-sdw.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sound/soc/codecs/rt1320-sdw.c b/sound/soc/codecs/rt1320-sdw.c
index 2999ab95971a..245b9d9980f9 100644
--- a/sound/soc/codecs/rt1320-sdw.c
+++ b/sound/soc/codecs/rt1320-sdw.c
@@ -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;) {
 
-- 
2.39.5

Re: [PATCH] ASoC: rt1320: fix size_t format string

[Mark Brown]

On Tue, 23 Dec 2025 22:53:19 +0100, Arnd Bergmann wrote:
> 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