linux-kernel - Re: [PATCH V2] spi: spi-cadence-quadspi: add runtime pm support

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: <169451868590.2398433.6752989625702796477.b4-ty@kernel.org>
Date:   Tue, 12 Sep 2023 12:38:05 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Dhruva Gole <d-gole@...com>
Cc:     linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        linux-spi@...r.kernel.org, Apurva Nandan <a-nandan@...com>,
        Sai Krishna Potthuri <lakshmi.sai.krishna.potthuri@...inx.com>,
        Ian Abbott <abbotti@....co.uk>,
        William Qiu <william.qiu@...rfivetech.com>,
        Brad Larson <blarson@....com>,
        Pratyush Yadav <ptyadav@...zon.de>,
        Vignesh Raghavendra <vigneshr@...com>,
        Vibhore Vardhan <vibhore@...com>
Subject: Re: [PATCH V2] spi: spi-cadence-quadspi: add runtime pm support

On Tue, 29 Aug 2023 11:57:08 +0530, Dhruva Gole wrote:
> Add runtime pm support to cadence-qspi driver, this allows the driver to
> suspend whenever it's is not actively being used thus reducing active
> power consumed by the system.
> 
> Also, with the use of devm_pm_runtime_enable we no longer need the
> fallback probe_pm_failed that used to pm_runtime_disable
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: spi-cadence-quadspi: add runtime pm support
      commit: 0578a6dbfe7514db7134501cf93acc21cf13e479

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