On Tue, 30 Apr 2024 16:02:09 +0200, Krzysztof Kozlowski wrote: > Do not open-code snd_soc_substream_to_rtd() when accessing > snd_pcm_substream->private_data. This makes code more consistent with > rest of ASoC and allows in the future to move the field to any other > place or add additional checks in snd_soc_substream_to_rtd(). > > Best regards, > Krzysztof > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [01/13] ASoC: qcom: Use snd_soc_substream_to_rtd() for accessing private_data commit: 77678a25d1ecf70dc1d7ea2c0ab7609af15b83d3 [02/13] ASoC: tegra: Use snd_soc_substream_to_rtd() for accessing private_data commit: 3beb985abbf29e660edd1708f8a120ae9bbbddc3 [03/13] ASoC: ti: Use snd_soc_substream_to_rtd() for accessing private_data commit: 72a666f47f958a57db16b6bdd9ed385674069693 [04/13] ASoC: arm: Use snd_soc_substream_to_rtd() for accessing private_data commit: a80f2f8443a4ae10c568566f57fe704ea52c5bdb [05/13] ASoC: amd: Use snd_soc_substream_to_rtd() for accessing private_data commit: a84d84077512fc64cf1fc2292a3638690a026737 [06/13] ASoC: fsl: Use snd_soc_substream_to_rtd() for accessing private_data commit: b695d8be5bba9897ee670ec102ca608ecaf625c4 [07/13] ASoC: img: Use snd_soc_substream_to_rtd() for accessing private_data commit: 3b62178720594e08bdf8a87515ccca0328fe41fe [08/13] ASoC: kirkwood: Use snd_soc_substream_to_rtd() for accessing private_data commit: fe42c3b75b93dee9a4010e2297f1783e48684af7 [09/13] ASoC: loongson: Use snd_soc_substream_to_rtd() for accessing private_data commit: ffad75cebb865fef6f8e40f921c08c79a8faf7e3 [10/13] ASoC: mediatek: Use snd_soc_substream_to_rtd() for accessing private_data commit: 410a45140fb76709cf2bbad84bc8a731acf632c8 [11/13] ASoC: meson: Use snd_soc_substream_to_rtd() for accessing private_data commit: 22f5680a9cbc7388f97e5386c15c325d6961b958 [12/13] ASoC: samsung: Use snd_soc_substream_to_rtd() for accessing private_data commit: 3e726593107d134221f666b4f2be612b278c3ddb [13/13] ASoC: sunxi: Use snd_soc_substream_to_rtd() for accessing private_data commit: 47aa51677c975a5f66bc93d1c527e8878cf34d6c 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
