linux-kernel - Re: [PATCH 1/1] spi: spi-qpic-snand: make qcom_spi_ecc_engine_ops

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: <176130144314.10577.9953872880836297632.b4-ty@kernel.org>
Date: Fri, 24 Oct 2025 11:24:03 +0100
From: Mark Brown <broonie@...nel.org>
To: Can Peng <pengcan@...inos.cn>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] spi: spi-qpic-snand: make
 qcom_spi_ecc_engine_ops_pipelined const

On Thu, 23 Oct 2025 10:42:50 +0800, Can Peng wrote:
> Marking the qcom_spi_ecc_engine_ops_pipelined as const provides
> memory protection by preventing accidental modification of critical
> function pointers at runtime. It also enables memory optimization
> by placing the structure in read-only sections and improves code safety
> by explicitly documenting the design intent that these operations
> should not change after initialization.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: spi-qpic-snand: make qcom_spi_ecc_engine_ops_pipelined const
      commit: fd5ef3d69f8975bad16c437a337b5cb04c8217a2

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