linux-kernel - Re: [PATCH] spi: spi-qpic-snand: remove superfluous qcom_spi_set_read

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: <176580716116.161463.15413695989499192950.b4-ty@kernel.org>
Date: Mon, 15 Dec 2025 22:59:21 +0900
From: Mark Brown <broonie@...nel.org>
To: Gabor Juhos <j4g8y7@...il.com>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Md Sadre Alam <quic_mdalam@...cinc.com>, 
 Varadarajan Narayanan <quic_varada@...cinc.com>, 
 Sricharan Ramabadhran <quic_srichara@...cinc.com>, 
 linux-mtd@...ts.infradead.org, linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH] spi: spi-qpic-snand: remove superfluous
 qcom_spi_set_read_loc() calls

On Sat, 29 Nov 2025 11:29:27 +0100, Gabor Juhos wrote:
> Before configuring the registers related to page read, both the
> qcom_spi_read_page_ecc() and the qcom_spi_read_page_oob() functions
> are calling qcom_spi_set_read_loc() to set the read location for the
> first codeword.
> 
> However the qcom_spi_set_read_loc() function puts the passed value
> into the register write cache only, from where those gets written
> to the corresponding register later via DMA.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: spi-qpic-snand: remove superfluous qcom_spi_set_read_loc() calls
      commit: cde4e63e847b4d41f017c2beb119c2668106a88a

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