linux-kernel - Re: [PATCH] driver:spi: change clk_disable_unprepare to clk

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: <164321140894.490397.924789471812651456.b4-ty@kernel.org>
Date:   Wed, 26 Jan 2022 15:36:48 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Romain Perier <romain.perier@...e-electrons.com>,
        Dongliang Mu <mudongliangabcd@...il.com>
Cc:     linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org
Subject: Re: [PATCH] driver:spi: change clk_disable_unprepare to clk_unprepare

On Mon, 6 Dec 2021 18:19:31 +0800, Dongliang Mu wrote:
> The corresponding API for clk_prepare is clk_unprepare, other than
> clk_disable_unprepare.
> 
> Fix this by changing clk_disable_unprepare to clk_unprepare.
> 
> 

Applied to

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

Thanks!

[1/1] driver:spi: change clk_disable_unprepare to clk_unprepare
      commit: 90cafce461de108bfb07c06148395dc86c3fcd23

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