[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <166446457527.149592.13835062357104188946.b4-ty@kernel.org>
Date: Thu, 29 Sep 2022 16:16:15 +0100
From: Mark Brown <broonie@...nel.org>
To: Banajit Goswami <bgoswami@...cinc.com>,
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Takashi Iwai <tiwai@...e.com>,
Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>,
Cezary Rojewski <cezary.rojewski@...el.com>,
Jaroslav Kysela <perex@...ex.cz>, alsa-devel@...a-project.org,
linux-kernel@...r.kernel.org,
Kai Vehmanen <kai.vehmanen@...ux.intel.com>,
Liam Girdwood <lgirdwood@...il.com>
Cc: Bard Liao <yung-chuan.liao@...ux.intel.com>,
stable@...r.kernel.org,
Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
Subject: Re: [PATCH] ASoC: wcd-mbhc-v2: Revert "ASoC: wcd-mbhc-v2: use pm_runtime_resume_and_get()"
On Thu, 29 Sep 2022 15:15:28 +0200, Krzysztof Kozlowski wrote:
> This reverts commit ddea4bbf287b6028eaa15a185d0693856956ecf2 ("ASoC:
> wcd-mbhc-v2: use pm_runtime_resume_and_get()"), because it introduced
> double runtime PM put if pm_runtime_get_sync() returns -EACCES:
>
> wcd934x-codec wcd934x-codec.3.auto: WCD934X Minor:0x1 Version:0x401
> wcd934x-codec wcd934x-codec.3.auto: Runtime PM usage count underflow!
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: wcd-mbhc-v2: Revert "ASoC: wcd-mbhc-v2: use pm_runtime_resume_and_get()"
commit: e18f6bcf8e864ea0e9690691d0d749c662b6a2c7
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
Powered by blists - more mailing lists