linux-kernel - Re: [PATCH] spi: coldfire-qspi: Remove an erroneous clk_disable

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]

Date: Fri, 05 Jan 2024 18:36:09 +0000
From: Mark Brown <broonie@...nel.org>
To: Yuanjun Gong <ruc_gongyuanjun@....com>, 
 Christophe JAILLET <christophe.jaillet@...adoo.fr>
Cc: alexis.lothore@...tlin.com, linux-kernel@...r.kernel.org, 
 kernel-janitors@...r.kernel.org, linux-spi@...r.kernel.org
Subject: Re: [PATCH] spi: coldfire-qspi: Remove an erroneous
 clk_disable_unprepare() from the remove function

On Fri, 05 Jan 2024 15:21:00 +0100, Christophe JAILLET wrote:
> The commit in Fixes has changed a devm_clk_get()/clk_prepare_enable() into
> a devm_clk_get_enabled().
> It has updated the error handling path of the probe accordingly, but the
> remove has been left unchanged.
> 
> Remove now the redundant clk_disable_unprepare() call from the remove
> function.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: coldfire-qspi: Remove an erroneous clk_disable_unprepare() from the remove function
      commit: 17dc11a02d8dacc7e78968daa2a8c16281eb7d1e

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