All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: lgirdwood@gmail.com, Zhang Qilong <zhangqilong3@huawei.com>,
	perex@perex.cz, ckeepax@opensource.wolfsonmicro.com,
	matthias.bgg@gmail.com, tiwai@suse.com, jeff_chang@richtek.com
Cc: alsa-devel@alsa-project.org, linux-mediatek@lists.infradead.org,
	patches@opensource.cirrus.com
Subject: Re: [PATCH v2 -next 0/4] Fix PM disable depth imbalance in probe
Date: Mon, 03 Oct 2022 17:47:49 +0100	[thread overview]
Message-ID: <166481566916.272202.9369598232153225882.b4-ty@kernel.org> (raw)
In-Reply-To: <20220929150653.63845-1-zhangqilong3@huawei.com>

On Thu, 29 Sep 2022 23:06:49 +0800, Zhang Qilong wrote:
> The pm_runtime_enable will increase power disable depth. Thus
> a pairing decrement is needed on the error handling path to
> keep it balanced according to context. We fix it by calling
> pm_runtime_disable when error returns.
> 

Applied to

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

Thanks!

[1/4] ASoC: wm8997: Fix PM disable depth imbalance in wm8997_probe
      commit: 41a736ac20602f64773e80f0f5b32cde1830a44a
[2/4] ASoC: wm5110: Fix PM disable depth imbalance in wm5110_probe
      commit: 86b46bf1feb83898d89a2b4a8d08d21e9ea277a7
[3/4] ASoC: wm5102: Fix PM disable depth imbalance in wm5102_probe
      commit: fcbb60820cd3008bb44334a0395e5e57ccb77329
[4/4] ASoC: mt6660: Fix PM disable depth imbalance in mt6660_i2c_probe
      commit: b73f11e895e140537e7f8c7251211ccd3ce0782b

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


WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: lgirdwood@gmail.com, Zhang Qilong <zhangqilong3@huawei.com>,
	perex@perex.cz, ckeepax@opensource.wolfsonmicro.com,
	 matthias.bgg@gmail.com, tiwai@suse.com, jeff_chang@richtek.com
Cc: patches@opensource.cirrus.com, alsa-devel@alsa-project.org,
	linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v2 -next 0/4] Fix PM disable depth imbalance in probe
Date: Mon, 03 Oct 2022 17:47:49 +0100	[thread overview]
Message-ID: <166481566916.272202.9369598232153225882.b4-ty@kernel.org> (raw)
In-Reply-To: <20220929150653.63845-1-zhangqilong3@huawei.com>

On Thu, 29 Sep 2022 23:06:49 +0800, Zhang Qilong wrote:
> The pm_runtime_enable will increase power disable depth. Thus
> a pairing decrement is needed on the error handling path to
> keep it balanced according to context. We fix it by calling
> pm_runtime_disable when error returns.
> 

Applied to

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

Thanks!

[1/4] ASoC: wm8997: Fix PM disable depth imbalance in wm8997_probe
      commit: 41a736ac20602f64773e80f0f5b32cde1830a44a
[2/4] ASoC: wm5110: Fix PM disable depth imbalance in wm5110_probe
      commit: 86b46bf1feb83898d89a2b4a8d08d21e9ea277a7
[3/4] ASoC: wm5102: Fix PM disable depth imbalance in wm5102_probe
      commit: fcbb60820cd3008bb44334a0395e5e57ccb77329
[4/4] ASoC: mt6660: Fix PM disable depth imbalance in mt6660_i2c_probe
      commit: b73f11e895e140537e7f8c7251211ccd3ce0782b

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

  parent reply	other threads:[~2022-10-03 16:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-29 15:06 [PATCH v2 -next 0/4] Fix PM disable depth imbalance in probe Zhang Qilong
2022-09-29 15:06 ` Zhang Qilong
2022-09-29 15:06 ` [PATCH v2 -next 1/4] ASoC: wm8997: Fix PM disable depth imbalance in wm8997_probe Zhang Qilong
2022-09-29 15:06   ` Zhang Qilong
2022-10-03 10:05   ` Charles Keepax
2022-10-03 10:05     ` Charles Keepax
2022-09-29 15:06 ` [PATCH v2 -next 2/4] ASoC: wm5110: Fix PM disable depth imbalance in wm5110_probe Zhang Qilong
2022-09-29 15:06   ` Zhang Qilong
2022-10-03 10:05   ` Charles Keepax
2022-10-03 10:05     ` Charles Keepax
2022-09-29 15:06 ` [PATCH v2 -next 3/4] ASoC: wm5102: Fix PM disable depth imbalance in wm5102_probe Zhang Qilong
2022-09-29 15:06   ` Zhang Qilong
2022-10-03 10:05   ` Charles Keepax
2022-10-03 10:05     ` Charles Keepax
2022-09-29 15:06 ` [PATCH v2 -next 4/4] ASoC: mt6660: Fix PM disable depth imbalance in mt6660_i2c_probe Zhang Qilong
2022-09-29 15:06   ` Zhang Qilong
2022-09-30  8:39   ` AngeloGioacchino Del Regno
2022-09-30  8:39     ` AngeloGioacchino Del Regno
2022-10-03 17:37   ` [PATCH v2 " Mark Brown
2022-10-03 17:37     ` Mark Brown
2022-10-03 16:47 ` Mark Brown [this message]
2022-10-03 16:47   ` [PATCH v2 -next 0/4] Fix PM disable depth imbalance in probe Mark Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=166481566916.272202.9369598232153225882.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=ckeepax@opensource.wolfsonmicro.com \
    --cc=jeff_chang@richtek.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=patches@opensource.cirrus.com \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    --cc=zhangqilong3@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.