linux-kernel - Re: (subset) [PATCH v3 00/13] Tidy up ASoC VALUE control macros

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: <174111350895.235764.8799430713993803159.b4-ty@kernel.org>
Date: Tue, 04 Mar 2025 18:38:28 +0000
From: Mark Brown <broonie@...nel.org>
To: Charles Keepax <ckeepax@...nsource.cirrus.com>
Cc: lgirdwood@...il.com, peda@...ntia.se, andrei.simion@...rochip.com, 
 nuno.sa@...log.com, paul@...pouillou.net, oder_chiou@...ltek.com, 
 kiseok.jo@...ndevice.com, shenghao-ding@...com, kevin-lu@...com, 
 baojun.xu@...com, srinivas.kandagatla@...aro.org, 
 linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 patches@...nsource.cirrus.com
Subject: Re: (subset) [PATCH v3 00/13] Tidy up ASoC VALUE control macros

On Tue, 04 Mar 2025 14:04:47 +0000, Charles Keepax wrote:
> Tidy up the ASoC control value macros. Fix some drivers that should be
> using core macros that aren't, combine the existing core macros to be
> a little more consistent in style, and update the core macros to use
> each other where possible.
> 
> Change since v2:
>  - Fix typo in SOC_DOUBLE_RANGE_TLV refactor
> 
> [...]

Applied to

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

Thanks!

[13/13] ASoC: Tidy up SOC_DOUBLE_* and SOC_SINGLE_* helpers
        commit: 6db63090272768785e6bb4a3afa16650c1e96c54

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