linux-kernel - Re: [PATCH] ASoC: codecs: lpass-tx-macro: set active

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: <170119364524.61148.12462722203643682631.b4-ty@kernel.org>
Date:   Tue, 28 Nov 2023 17:47:25 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
        Banajit Goswami <bgoswami@...cinc.com>,
        Liam Girdwood <lgirdwood@...il.com>,
        Jaroslav Kysela <perex@...ex.cz>,
        Takashi Iwai <tiwai@...e.com>,
        Neil Armstrong <neil.armstrong@...aro.org>
Cc:     krzysztof.kozlowski@...aro.org,
        linux-arm-msm-owner@...r.kernel.org, alsa-devel@...a-project.org,
        linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: codecs: lpass-tx-macro: set active_decimator
 correct default value

On Thu, 16 Nov 2023 17:44:21 +0100, Neil Armstrong wrote:
> The -1 value for active_decimator[dai_id] is considered as "not set",
> but at probe the table is initialized a 0, this prevents enabling the
> DEC0 Mixer since it will be considered as already set.
> 
> Initialize the table entries as -1 to fix tx_macro_tx_mixer_put().
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: codecs: lpass-tx-macro: set active_decimator correct default value
      commit: 69cecaf48831480252dcb63ba32803724f235b1c

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