linux-kernel - Re: [PATCH 0/3] spi: atmel-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: <165487674116.1756526.16695078743655371627.b4-ty@kernel.org>
Date:   Fri, 10 Jun 2022 16:59:01 +0100
From:   Mark Brown <broonie@...nel.org>
To:     tudor.ambarus@...rochip.com, nicolas.ferre@...rochip.com,
        alexandre.belloni@...tlin.com, claudiu.beznea@...rochip.com
Cc:     linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 0/3] spi: atmel-quadspi: add runtime pm support

On Thu, 9 Jun 2022 11:42:43 +0300, Claudiu Beznea wrote:
> The following series adds runtime PM support for atmel-quadspi driver.
> clk_disable()/clk_enable() is called on proper
> runtime_suspend()/runtime_resume() ops. Along with it 2 minor cleanups
> were added (patches 2/3, 3/3).
> 
> Thank you,
> Claudiu Beznea
> 
> [...]

Applied to

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

Thanks!

[1/3] spi: atmel-quadspi: add runtime pm support
      commit: c349fad389c5916facead610d454250f67cfb20b
[2/3] spi: atmel-quadspi: use pm_ptr()
      commit: f11ec1cc46e38f0feac3721a03c21fa99167e329
[3/3] spi: atmel-quadspi: align condition to parenthesis
      commit: af7c2d4145b57c15d25a092cfb5a91708c72b541

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