On Mon, 26 Aug 2024 13:44:02 +0800, Shen Lichuan wrote:

Let the kmemdup_array() take care about multiplication and possible overflows.

Using kmemdup_array() is more appropriate and makes the code easier to audit.

[...]

Applied to

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

Thanks!

[1/1] ASoC: SOF: topology: Use kmemdup_array instead of kmemdup for multiple allocation commit: 69a8d0edb9d78bb5515133b7c08f399d6eaff37a

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