Re: [PATCH 0/8] ASoC: Intel: catpt: Code cleanup and renames

On Wed, 29 Jul 2026 13:00:49 +0200, Cezary Rojewski wrote:
> ASoC: Intel: catpt: Code cleanup and renames
> 
> Direct follow up to the cleanup from June [1] and fixes from May [2].
> Patches 4/8 and 5/8 is what I actually started with, several years ago
> when doing first attempts in addressing the long-standing problem [3].
> With these, it is easy for a developer to move between the driver and
> the firmware repository.  A clear example of why naming is imporant.
> 
> [...]

Applied to

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

Thanks!

[1/8] ASoC: Intel: catpt: Wrap the store firmware-context procedure
      https://git.kernel.org/broonie/sound/c/abc7daad426e
[2/8] ASoC: Intel: catpt: Drop redundant else-if
      https://git.kernel.org/broonie/sound/c/05d3ba625802
[3/8] ASoC: Intel: catpt: Drop redundant signature argument
      https://git.kernel.org/broonie/sound/c/f6c65bf0acc9
[4/8] ASoC: Intel: catpt: Rename module header struct
      https://git.kernel.org/broonie/sound/c/71d1229972e2
[5/8] ASoC: Intel: catpt: Rename firmware loading functions
      https://git.kernel.org/broonie/sound/c/e692a538a421
[6/8] ASoC: Intel: catpt: Streamline wording of offset variables
      https://git.kernel.org/broonie/sound/c/ae6540c4909a
[7/8] ASoC: Intel: catpt: Streamline runtime-variables naming
      https://git.kernel.org/broonie/sound/c/a0acf55be734
[8/8] ASoC: Intel: catpt: Streamline control-variables naming
      https://git.kernel.org/broonie/sound/c/4075b9d256ef

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