linux-kernel - Re: [PATCH] spi: spi-qpic-snand: simplify clock handling by using devm_clk_get

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: <175829110428.130975.7186630185798573706.b4-ty@kernel.org>
Date: Fri, 19 Sep 2025 15:11:44 +0100
From: Mark Brown <broonie@...nel.org>
To: Gabor Juhos <j4g8y7@...il.com>
Cc: Varadarajan Narayanan <quic_varada@...cinc.com>, 
 Sricharan Ramabadhran <quic_srichara@...cinc.com>, 
 Md Sadre Alam <quic_mdalam@...cinc.com>, linux-spi@...r.kernel.org, 
 linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: spi-qpic-snand: simplify clock handling by using
 devm_clk_get_enabled()

On Tue, 16 Sep 2025 19:43:46 +0200, Gabor Juhos wrote:
> The devm_clk_get_enabled() function prepares and enables the
> particular clock, which then automatically gets disabled and
> unprepared on probe failure and on device removal.
> 
> Use that function instead of devm_clk_get() and remove the
> clk_prepare_enable()/clk_disable_unprepare() calls in order
> to simplify the code.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: spi-qpic-snand: simplify clock handling by using devm_clk_get_enabled()
      commit: a24802b0a2a238eaa610b0b0e87a4500a35de64a

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