[v3] spi: geni-qcom: Undo runtime PM changes at driver exit time

[PATCH v3 0/3] spi: geni-qcom: Undo runtime PM changes at driver exit time

Posted by Jinjie Ruan 2 months, 3 weeks ago

Fix two bugs for geni-qcom and use dev managed function
to simplify code.

Changes in v3:
- Adjust the runtime PM patch to be the first.
- Use devm_pm_runtime_enable() to undo runtime PM changes.
- Land the rest of the cleanups afterwards.
- Update the commit message.

Changes in v2:
- Split out the device managed cleanup patch.
- PATCH -next -> PATCH
- Also fix the incorrect free_irq() sequence.

Jinjie Ruan (3):
  spi: geni-qcom: Undo runtime PM changes at driver exit time
  spi: geni-qcom: Fix incorrect free_irq() sequence
  spi: geni-qcom: Use devm functions to simplify code

 drivers/spi/spi-geni-qcom.c | 50 ++++++++++++++-----------------------
 1 file changed, 19 insertions(+), 31 deletions(-)

-- 
2.34.1

Re: (subset) [PATCH v3 0/3] spi: geni-qcom: Undo runtime PM changes at driver exit time

Posted by Mark Brown 2 months, 3 weeks ago

On Mon, 09 Sep 2024 15:31:38 +0800, Jinjie Ruan wrote:
> Fix two bugs for geni-qcom and use dev managed function
> to simplify code.
> 
> Changes in v3:
> - Adjust the runtime PM patch to be the first.
> - Use devm_pm_runtime_enable() to undo runtime PM changes.
> - Land the rest of the cleanups afterwards.
> - Update the commit message.
> 
> [...]

Applied to

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

Thanks!

[1/3] spi: geni-qcom: Undo runtime PM changes at driver exit time
      commit: 89e362c883c65ff94b76b9862285f63545fb5274
[2/3] spi: geni-qcom: Fix incorrect free_irq() sequence
      commit: b787a33864121a565aeb0e88561bf6062a19f99c

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