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
| ||
|
Message-Id: <166938640983.506633.5904617504530907005.b4-ty@kernel.org> Date: Fri, 25 Nov 2022 14:26:49 +0000 From: Mark Brown <broonie@...nel.org> To: Richard Fitzgerald <rf@...nsource.cirrus.com> Cc: linux-kernel@...r.kernel.org, patches@...nsource.cirrus.com, alsa-devel@...a-project.org Subject: Re: [PATCH v2 0/2] ASoC: wm_adsp: Report when a control write changes the value On Wed, 23 Nov 2022 16:58:09 +0000, Richard Fitzgerald wrote: > Writing a firmware control should be returning 1 if the control value > changed, so these two patches add that. > > Though this is an ALSA requirement it is also useful for non-ALSA clients > of cs_dsp to know if the control value changed, so the main handling is > implemented in cs_dsp. TLV controls are specifically an ALSA thing so they > are handled specially in wm_adsp. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/2] firmware: cs_dsp: cs_dsp_coeff_write_ctrl() should report changed commit: c56f4b2442d33bd94c418697f753271099384bee [2/2] ASoC: wm_adsp: Return whether changed when writing controls commit: 7406bdbc4fb8b99cf0150cb2056a585c95ceafe7 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
Powered by blists - more mailing lists