linux-kernel - Re: [PATCH 0/5] ASoC: qdsp6: fixes and improve error reporting

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: <163708489246.808719.13508862895307481528.b4-ty@kernel.org>
Date:   Tue, 16 Nov 2021 17:48:12 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Cc:     linux-kernel@...r.kernel.org, perex@...ex.cz, tiwai@...e.com,
        pierre-louis.bossart@...ux.intel.com, alsa-devel@...a-project.org,
        lgirdwood@...il.com
Subject: Re: [PATCH 0/5] ASoC: qdsp6: fixes and improve error reporting

On Tue, 16 Nov 2021 11:47:16 +0000, Srinivas Kandagatla wrote:
> During testing on a laptop we found few issues with the existing q6dsp code,
> first 3 patches should fix these issues. Also during debug we found that
> some of the errors reported are not very useful, so update error reporting
> in two places.
> 
> Thanks,
> srini
> 
> [...]

Applied to

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

Thanks!

[1/5] ASoC: qdsp6: qdsp6: q6prm: handle clk disable correctly
      commit: 2f20640491edda3c03eb6b899d0b92630d3d4c63
[2/5] ASoC: qdsp6: q6routing: Conditionally reset FrontEnd Mixer
      commit: 861afeac7990587588d057b2c0b3222331c3da29
[3/5] ASoC: qdsp6: q6asm: fix q6asm_dai_prepare error handling
      commit: 721a94b4352dc8e47bff90b549a0118c39776756
[4/5] ASoC: qdsp6: q6adm: improve error reporting
      commit: 0a270471d68533f59c5cfd631a3fce31a3b17144
[5/5] ASoC: qdsp6: q6routing: validate port id before setting up route
      commit: 6712c2e18c06b0976559fd4bd47774b243038e9c

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