Re: [PATCH -next 0/3] Fix PM disable depth imbalance in probe

From: Mark Brown <broonie@kernel.org>
To: Zhang Qilong <zhangqilong3@huawei.com>
Cc: linux-spi@vger.kernel.org
Subject: Re: [PATCH -next 0/3] Fix PM disable depth imbalance in probe
Date: Tue, 27 Sep 2022 11:34:30 +0100	[thread overview]
Message-ID: <166427487094.61277.8173045546114429378.b4-ty@kernel.org> (raw)
In-Reply-To: <20220924121310.78331-1-zhangqilong3@huawei.com>

On Sat, 24 Sep 2022 20:13:06 +0800, Zhang Qilong wrote:
> The pm_runtime_enable will increase power disable depth. Thus
> a pairing decrement is needed when error returns to keep it
> balanced. This series of patches fixed it in spi probe.
> 
> Zhang Qilong (3):
>   spi: cadence-quadspi: Fix PM disable depth imbalance in cqspi_probe
>   spi: dw: Fix PM disable depth imbalance in dw_spi_bt1_probe
>   spi/omap100k:Fix PM disable depth imbalance in omap1_spi100k_probe
> 
> [...]

Applied to

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

Thanks!

[1/3] spi: cadence-quadspi: Fix PM disable depth imbalance in cqspi_probe
      commit: 4d0ef0a1c35189a6e8377d8ee8310ea5ef22c5f3
[2/3] spi: dw: Fix PM disable depth imbalance in dw_spi_bt1_probe
      commit: 618d815fc93477b1675878f3c04ff32657cc18b4
[3/3] spi/omap100k:Fix PM disable depth imbalance in omap1_spi100k_probe
      commit: 29f65f2171c85a9633daa380df14009a365f42f2

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