linux-kernel - Re: [PATCH RESEND] ASoC: mediatek: mt8195: optimize property formatting error handling by using scnprintf()

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <176580712756.161056.16246291831827319109.b4-ty@kernel.org>
Date: Mon, 15 Dec 2025 22:58:47 +0900
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, matthias.bgg@...il.com, 
 angelogioacchino.delregno@...labora.com, hariconscious@...il.com
Cc: perex@...ex.cz, tiwai@...e.com, khalid@...nel.org, shuah@...nel.org, 
 david.hunter.linux@...il.com, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, 
 linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH RESEND] ASoC: mediatek: mt8195: optimize property
 formatting error handling by using scnprintf()

On Fri, 12 Dec 2025 10:14:09 +0530, hariconscious@...il.com wrote:
> Replace snprintf() with scnprintf() when constructing the property
> and remove negative return error handling as scnprintf() returns the
> actual number of bytes written to buffer.
> 
> snprintf() as defined by the C99 standard,returns the number of
> characters that *would have been* written if enough space were
> available.Use scnprintf() that returns the actual number of
> characters written.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: mediatek: mt8195: optimize property formatting error handling by using scnprintf()
      commit: 180cdb96e821e30528b02708b927c93daa0ed40b

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