linux-kernel - Re: [PATCH v1 1/2] spi: tegra20-slink: Put device into suspend on driver removal

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:   Mon, 25 Oct 2021 17:39:19 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Thierry Reding <treding@...dia.com>,
        Sowjanya Komatineni <skomatineni@...dia.com>,
        Dmitry Osipenko <digetx@...il.com>,
        Jonathan Hunter <jonathanh@...dia.com>,
        Laxman Dewangan <ldewangan@...dia.com>
Cc:     Mark Brown <broonie@...nel.org>, linux-kernel@...r.kernel.org,
        linux-tegra@...r.kernel.org, linux-spi@...r.kernel.org
Subject: Re: [PATCH v1 1/2] spi: tegra20-slink: Put device into suspend on driver removal

On Sun, 24 Oct 2021 01:59:50 +0300, Dmitry Osipenko wrote:
> pm_runtime_disable() cancels all pending power requests, while they
> should be completed for the Tegra SPI driver. Otherwise SPI clock won't
> be disabled ever again because clk refcount will become unbalanced.
> Enforce runtime PM suspension to put device into expected state before
> driver is unbound and device's RPM state is reset by driver's core.
> 
> 
> [...]

Applied to

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

Thanks!

[1/2] spi: tegra20-slink: Put device into suspend on driver removal
      commit: f4bafa944553f606e0f471fadfb64d84afe70fb0
[2/2] spi: tegra210-quad: Put device into suspend on driver removal
      commit: 186640328685ef09d2c575fb26a243d3ac7963aa

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