linux-kernel - Re: [PATCH v2] ASoC: cs42l42: Add control for audio slow-start switch

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: <163701929762.675370.12528564443192014904.b4-ty@kernel.org>
Date:   Mon, 15 Nov 2021 23:34:57 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc:     linux-kernel@...r.kernel.org, alsa-devel@...a-project.org,
        patches@...nsource.cirrus.com
Subject: Re: [PATCH v2] ASoC: cs42l42: Add control for audio slow-start switch

On Mon, 1 Nov 2021 10:10:06 +0000, Richard Fitzgerald wrote:
> This adds an ALSA control so that the slow-start audio ramp feature
> can be disabled. This is useful for high-definition audio applications.
> 
> The register field is unusual in that it is a 3-bit field with only
> two valid values, 000=off and 111=on.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: cs42l42: Add control for audio slow-start switch
      commit: 7ec4a058c16f3da9c2c0c66506f45c083198ed30

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