linux-kernel - Re: [PATCH v2] ASoC: SOF: Remove pm_runtime_put

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]

Date:   Tue, 14 Dec 2021 13:25:24 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Daniel Baluta <daniel.baluta@....nxp.com>
Cc:     ranjani.sridharan@...ux.intel.com,
        linux-mediatek@...ts.infradead.org,
        Allen-KH Cheng <Allen-KH.Cheng@...iatek.com>,
        pierre-louis.bossart@...ux.intel.com, kai.vehmanen@...ux.intel.com,
        Paul Olaru <paul.olaru@....nxp.com>,
        linux-kernel@...r.kernel.org,
        Daniel Baluta <daniel.baluta@....com>, lgirdwood@...il.com,
        alsa-devel@...a-project.org
Subject: Re: [PATCH v2] ASoC: SOF: Remove pm_runtime_put_autosuspend() for SOF OF device

On Thu, 9 Dec 2021 22:08:30 +0200, Daniel Baluta wrote:
> From: Allen-KH Cheng <Allen-KH.Cheng@...iatek.com>
> 
> In SOF OF device, pm_runtime_put_autosuspend() is not
> matching any pm_runtime_get_sync().
> 
> This is imbalanced for PM runtime.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: SOF: Remove pm_runtime_put_autosuspend() for SOF OF device
      commit: 475b17b4a875ef31246c6a038ee60d5ca4982ea5

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