linux-kernel - Re: [PATCH] ASoC: cs43130: Constify snd_soc_component

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: <172263399662.130801.3172998123321447676.b4-ty@kernel.org>
Date: Fri, 02 Aug 2024 22:26:36 +0100
From: Mark Brown <broonie@...nel.org>
To: ckeepax@...nsource.cirrus.com, javier.carrasco.cruz@...il.com, 
 David Rhodes <david.rhodes@...rus.com>, 
 Richard Fitzgerald <rf@...nsource.cirrus.com>, 
 Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, 
 Christophe JAILLET <christophe.jaillet@...adoo.fr>
Cc: linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org, 
 alsa-devel@...a-project.org, patches@...nsource.cirrus.com, 
 linux-sound@...r.kernel.org
Subject: Re: [PATCH] ASoC: cs43130: Constify snd_soc_component_driver
 struct

On Mon, 29 Jul 2024 19:36:05 +0200, Christophe JAILLET wrote:
> In order to constify `snd_soc_component_driver` struct, duplicate
> `soc_component_dev_cs43130` into a `soc_component_dev_cs43130_digital` and
> `soc_component_dev_cs43130_analog`.
> 
> These 2 new structures share the same .dapm_widgets and .dapm_routes
> arrays but differ for .num_dapm_widgets and .num_dapm_routes.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: cs43130: Constify snd_soc_component_driver struct
      commit: 839e231a53b824a62bc3696ad3ba1dcedc4f4167

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