linux-kernel - Re: [PATCH] spi: zynq-qspi: Replace kzalloc with kmalloc for buffer allocation

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: <172536341582.28645.16590176643988144585.b4-ty@kernel.org>
Date: Tue, 03 Sep 2024 12:36:55 +0100
From: Mark Brown <broonie@...nel.org>
To: Kuan-Wei Chiu <visitorckw@...il.com>
Cc: Michal Simek <michal.simek@....com>, 
 Ching-Chun Huang <jserv@...s.ncku.edu.tw>, linux-spi@...r.kernel.org, 
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: zynq-qspi: Replace kzalloc with kmalloc for
 buffer allocation

On Thu, 15 Aug 2024 03:28:39 +0800, Kuan-Wei Chiu wrote:
> In zynq_qspi_exec_mem_op(), the temporary buffer is allocated with
> kzalloc and then immediately initialized using memset to 0xff. To
> optimize this, replace kzalloc with kmalloc, as the zeroing operation
> is redundant and unnecessary.
> 
> 

Applied to

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

Thanks!

[1/1] spi: zynq-qspi: Replace kzalloc with kmalloc for buffer allocation
      commit: f626a0cd07ddb13f146e52adb4b534da40bb1ff7

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