[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <162256892744.19919.16377116740112548750.b4-ty@kernel.org>
Date: Tue, 1 Jun 2021 18:38:08 +0100
From: Mark Brown <broonie@...nel.org>
To: Rikard Falkeborn <rikard.falkeborn@...il.com>,
Liam Girdwood <lgirdwood@...il.com>
Cc: Mark Brown <broonie@...nel.org>, Takashi Iwai <tiwai@...e.com>,
alsa-devel@...a-project.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/5] ASoC: Constify snd_compress_ops
On Thu, 27 May 2021 01:10:08 +0200, Rikard Falkeborn wrote:
> The only use of the static and global snd_compress_ops structs is to
> assign their address to the compress_ops field in the
> snd_soc_component_driver struct which is a pointer to const. Make them
> const to allow the compiler to put them in read-only memory.
>
> Rikard Falkeborn (5):
> ASoC: cs47125: Constify static struct snd_compress_ops
> ASoC: wm5102: Constify static struct snd_compress_ops
> ASoC: wm5110: Constify static struct snd_compress_ops
> ASoC: qcom: q6asm-dai: Constify static struct snd_compress_ops
> ASoC: SOF: Intel: Constify sof_probe_compressed_ops
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/5] ASoC: cs47125: Constify static struct snd_compress_ops
commit: 44b9f90705bb580a9616ecd5498dd30943c1f1ce
[2/5] ASoC: wm5102: Constify static struct snd_compress_ops
commit: b6f5d62e7afc398c375855c0d8105e5561f9fc37
[3/5] ASoC: wm5110: Constify static struct snd_compress_ops
commit: 4127a3a541ac35360cb45909944747d61c606f0a
[4/5] ASoC: qcom: q6asm-dai: Constify static struct snd_compress_ops
commit: a8048051d7ce2349e4cda28954ded733d6c42028
[5/5] ASoC: SOF: Intel: Constify sof_probe_compressed_ops
commit: 7db43da8c0990bb1276d1b7b185b1b9f9be6dcbb
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