[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <171916330129.350242.13312693360705760410.b4-ty@kernel.org>
Date: Sun, 23 Jun 2024 18:21:41 +0100
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>,
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
Banajit Goswami <bgoswami@...cinc.com>,
Cezary Rojewski <cezary.rojewski@...el.com>,
Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
Peter Ujfalusi <peter.ujfalusi@...ux.intel.com>,
Bard Liao <yung-chuan.liao@...ux.intel.com>,
Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>,
Kai Vehmanen <kai.vehmanen@...ux.intel.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org,
alsa-devel@...a-project.org, linux-arm-msm@...r.kernel.org
Subject: Re: (subset) [PATCH 0/6] ASoC: Few constifications (mostly
arguments)
On Mon, 17 Jun 2024 15:03:18 +0200, Krzysztof Kozlowski wrote:
> Make few pointers in ASoC functions as pointers to const, so the code is
> clearer to read, a bit safer and allows further constifications (e.g.
> placing some data as rodata).
>
> Best regards,
> Krzysztof
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/6] ASoC: Constify of_phandle_args in snd_soc_dai_driver
commit: 2fbafecb0f05818e25f6c926c6f9ad9ef597429c
[2/6] ASoC: Constify of_phandle_args in snd_soc_dai_link_component
commit: 020b37d06f97de289940805bc821190d5858eda0
[3/6] ASoC: Constify passed data to core function
commit: f3ac3da7e4d0957b3402fb31a4ca480e739e086f
[4/6] ASoC: Constify DAI passed to get_channel_map
commit: 785d64c4941221044940ab199e6625af17296470
[5/6] ASoC: Constify return of snd_soc_dai_get_pcm_stream()
commit: de267e7a6ea8e6fa29af2287adfc9fc9d87e6dc9
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