linux-kernel - Re: [PATCH 0/3] spi: Fix pm_runtime_set

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: <172782953505.2314893.17571389802894032721.b4-ty@kernel.org>
Date: Wed, 02 Oct 2024 01:38:55 +0100
From: Mark Brown <broonie@...nel.org>
To: shawnguo@...nel.org, s.hauer@...gutronix.de, kernel@...gutronix.de, 
 festevam@...il.com, shubhrajyoti.datta@...inx.com, srinivas.goud@....com, 
 linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 imx@...ts.linux.dev, linux-arm-kernel@...ts.infradead.org, 
 Jinjie Ruan <ruanjinjie@...wei.com>
Subject: Re: [PATCH 0/3] spi: Fix pm_runtime_set_suspended() with runtime
 pm enabled

On Mon, 23 Sep 2024 12:00:12 +0800, Jinjie Ruan wrote:
> Fix pm_runtime_set_suspended() with runtime pm enabled, and fix the missing
> check for spi-cadence.
> 
> Jinjie Ruan (3):
>   spi: spi-imx: Fix pm_runtime_set_suspended() with runtime pm enabled
>   spi: spi-cadence: Fix pm_runtime_set_suspended() with runtime pm
>     enabled
>   spi: spi-cadence: Fix missing spi_controller_is_target() check
> 
> [...]

Applied to

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

Thanks!

[1/3] spi: spi-imx: Fix pm_runtime_set_suspended() with runtime pm enabled
      commit: b6e05ba0844139dde138625906015c974c86aa93
[2/3] spi: spi-cadence: Fix pm_runtime_set_suspended() with runtime pm enabled
      commit: 67d4a70faa662df07451e83db1546d3ca0695e08
[3/3] spi: spi-cadence: Fix missing spi_controller_is_target() check
      commit: 3eae4a916fc0eb6f85b5d399e10335dbd24dd765

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