linux-kernel - Re: [PATCH] ASoC: tas571x: fix tas5733 num

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: <174843843382.44834.14730284248939713769.b4-ty@kernel.org>
Date: Wed, 28 May 2025 14:20:33 +0100
From: Mark Brown <broonie@...nel.org>
To: Kevin Cernekee <cernekee@...omium.org>, 
 Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, 
 Bram Vlerick <bram.vlerick@...npixelsystems.org>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 peter@...sgaard.com, kamel.bouhara@...tlin.com
Subject: Re: [PATCH] ASoC: tas571x: fix tas5733 num_controls

On Wed, 28 May 2025 10:25:48 +0200, Bram Vlerick wrote:
> Commit e3de7984e451 ("ASoC: tas571x: add separate tas5733 controls")
> introduces a separate struct for the tas5733 controls but did not update
> the num_controls with the correct ARRAY_SIZE.
> 
> Fixes: e3de7984e451 ("ASoC: tas571x: add separate tas5733 controls")
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: tas571x: fix tas5733 num_controls
      commit: bc4005ef43104da589951dba69291360c6a11ae7

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