Re: [PATCH 0/5] spi: replace strcpy(), sprintf() and simple_strtoul() with strscpy(), snprintf() and kstrtoul()

[Mark Brown]

On Fri, 09 Oct 2026 19:06:04 +0530, Aayush Kumar wrote:
> spi: replace strcpy(), sprintf() and simple_strtoul() with strscpy(), snprintf() and kstrtoul()
> 
> Replace strcpy(), sprintf() and simple_strtoul() with their safer
> modern equivalents (strscpy, snprintf, kstrtoul).
> 
> Aayush Kumar (5):
>   spi: butterfly: Use strscpy() instead of strcpy()
>   spi: lm70llp: Use strscpy() instead of strcpy()
>   spi: tle62x0: Use kstrtoul() instead of simple_strtoul()
>   spi: omap2-mcspi: Use snprintf() instead of sprintf()
>   spi: s3c64xx: Use snprintf() instead of sprintf()
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-7.4

Thanks!

[1/5] spi: butterfly: Use strscpy() instead of strcpy()
      https://git.kernel.org/broonie/spi/c/e9b641d92963
[2/5] spi: lm70llp: Use strscpy() instead of strcpy()
      https://git.kernel.org/broonie/spi/c/ae6056b248eb
[3/5] spi: tle62x0: Use kstrtoul() instead of simple_strtoul()
      https://git.kernel.org/broonie/spi/c/9a6b86cee9d7
[4/5] spi: omap2-mcspi: Use snprintf() instead of sprintf()
      https://git.kernel.org/broonie/spi/c/50f3d77e805f
[5/5] spi: s3c64xx: Use snprintf() instead of sprintf()
      https://git.kernel.org/broonie/spi/c/65f9474caced

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