linux-kernel - Re: [PATCH next] spi: spi-qpic-snand: remove superfluous parameters of qcom_spi_check

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: <174790605671.30110.1298547023446316402.b4-ty@kernel.org>
Date: Thu, 22 May 2025 10:27:36 +0100
From: Mark Brown <broonie@...nel.org>
To: Gabor Juhos <j4g8y7@...il.com>
Cc: Md Sadre Alam <quic_mdalam@...cinc.com>, 
 Varadarajan Narayanan <quic_varada@...cinc.com>, 
 Sricharan Ramabadhran <quic_srichara@...cinc.com>, 
 linux-spi@...r.kernel.org, linux-mtd@...ts.infradead.org, 
 linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH next] spi: spi-qpic-snand: remove superfluous
 parameters of qcom_spi_check_error()

On Tue, 20 May 2025 21:08:56 +0200, Gabor Juhos wrote:
> The qcom_spi_check_error() function determines the errors of a previous
> page read operation solely by using the cached register values in the
> register read buffer. The data pointed by the 'data_buf' and the 'oob_buf'
> parameters are not used for that at all.
> 
> Remove the superfluous parameters of the function along with the related
> local variables to simplify the code. Also, remove the variables from the
> caller functions which became unused due to the change.
> 
> [...]

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 parameters of qcom_spi_check_error()
      commit: 0f529570ecaf99244dc86b8af13618f0d07b0e44

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