[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <176644417935.2691602.16694159244085079057.b4-ty@kernel.org>
Date: Mon, 22 Dec 2025 22:56:19 +0000
From: Mark Brown <broonie@...nel.org>
To: Srinivas Kandagatla <srini@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@....qualcomm.com>
Cc: linux-sound@...r.kernel.org, linux-arm-msm@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/5] ASoC: qcom: Constify few things in audioreach
and topology
On Fri, 19 Dec 2025 12:45:43 +0100, Krzysztof Kozlowski wrote:
> Changes in v2:
> - Drop first patch (one removing unused arguments)
> - Rebase (new speaker_protection functions appear)
> - Link to v1: https://patch.msgid.link/20251129-b4-container-of-const-asoc-qcom-v1-0-67a3d3320371@oss.qualcomm.com
>
> Several functions do not modify the pointed memory they receive, so
> marking them as pointers to const would serve as self-explanatory code.
> Also safer a bit.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/5] ASoC: qcom: topology: Constify pointed topology and vendor structs
commit: c4be067a7b67f616b9ec85423a20be6be9b8ec37
[2/5] ASoC: qcom: topology: Constify pointed ar control structs
commit: 5e357c7e5e0920bd806a4e7c446c83715315f923
[3/5] ASoC: qcom: topology: Constify pointed DAPM widget structs
commit: 61fc95c4e3b26b3d1259a87124bdc25e4f71a8df
[4/5] ASoC: qcom: topology: Constify pointed snd_soc_tplg_dapm_widget
commit: 49675f5e750a2a5d530c56d130017d0337eed18f
[5/5] ASoC: qcom: audioreach: Constify function arguments
commit: 4ab48cc63e15cb619d641d1edf9a15a0a98875b2
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