linux-kernel - Re: [PATCH 0/6] Suspend related fixes on Tegra

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:   Sat, 27 Nov 2021 01:29:37 +0000
From:   Mark Brown <broonie@...nel.org>
To:     tiwai@...e.com, lgirdwood@...il.com,
        Sameer Pujar <spujar@...dia.com>, perex@...ex.cz
Cc:     jonathanh@...dia.com, thierry.reding@...il.com,
        linux-kernel@...r.kernel.org, alsa-devel@...a-project.org,
        linux-tegra@...r.kernel.org
Subject: Re: [PATCH 0/6] Suspend related fixes on Tegra

On Tue, 23 Nov 2021 19:37:33 +0530, Sameer Pujar wrote:
> This series addresses following problems:
>  * The runtime PM is not balanced in MVC driver, whenever
>    mute or volume mixer controls are set.
>  * Some of the AHUB devices (SFC, MVC, Mixer, AMX and ADX)
>    use late system sleep. Suspend failure is seen on Jetson
>    TX2 platform.
> 
> [...]

Applied to

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

Thanks!

[1/6] ASoC: tegra: Balance runtime PM count
      commit: 70408f755f589f67957b9ec6852e6b01f858d0a2
[2/6] ASoC: tegra: Use normal system sleep for SFC
      commit: af120d07bbb0721708b10204beed66ed2cb0cb62
[3/6] ASoC: tegra: Use normal system sleep for MVC
      commit: c83d263a89f30d1c0274827c475f3583cf8e477f
[4/6] ASoC: tegra: Use normal system sleep for Mixer
      commit: b78400e41653b3a752a4cd17d2fcbd4a96bb4bc2
[5/6] ASoC: tegra: Use normal system sleep for AMX
      commit: 638c31d542a576714a52bb6a9a7dedff98e32a1d
[6/6] ASoC: tegra: Use normal system sleep for ADX
      commit: cf36de4fc5ce5502ce5070a793addd9d49df4113

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