linux-kernel - Re: [v2] ASoC: max98390: Remove unnecessary amp on/off conrtol

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]

Message-Id: <166264096268.88408.10282562173881107177.b4-ty@kernel.org>
Date:   Thu, 08 Sep 2022 13:42:42 +0100
From:   Mark Brown <broonie@...nel.org>
To:     perex@...ex.cz, linux-kernel@...r.kernel.org,
        Steve Lee <steve.lee.analog@...il.com>, lgirdwood@...il.com,
        tiwai@...e.com, alsa-devel@...a-project.org
Cc:     ryans.lee@...log.com, krzk@...nel.org
Subject: Re: [v2] ASoC: max98390: Remove unnecessary amp on/off conrtol

On Thu, 8 Sep 2022 15:03:59 +0900, Steve Lee wrote:
>  The Amp is already control in userspace before trigger calibrate function.
> Remove unnecessary control in calibrate function and
> add condition to check calibration is ready.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: max98390: Remove unnecessary amp on/off conrtol
      commit: 6ac246105b4fd737ed51b8ac3ef031f837686dee

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