[PATCH 00/11] ASoC: SOF: Extend the IPC ops optionality

[Mark Brown]

On Wed, 21 Dec 2022 12:23:17 +0200, Peter Ujfalusi wrote:
> This series will extend the IPC ops optionality to cover it up to the existence
> of the top level ipc pointer itself. There is no functionality change.
> 
> The reason for the extended optionality is that we have "DSPless"
> debug/development support coming up (currently it is in SOF's topic/sof-dev
> stable branch) initially supporting Intel's HDA platforms.
> 
> [...]

Applied to

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

Thanks!

[01/11] ASoC: SOF: sof-audio: Treat tplg_ops->route_setup() as optional
        commit: 5315411729b188a8d39252a8c4b9bbdbc3ba6d92
[02/11] ASoC: SOF: sof-audio: Update documentation for sof_ipc_tplg_ops
        commit: 7cbb15593223e1fa56717fd33222c9a804162d70
[03/11] ASoC: SOF: Add helper macro to be used to get an IPC ops
        commit: caf0f4662e07fcc721d1c85af82aa8a7d57621f3
[04/11] ASoC: SOF: pcm: Extend the optionality of IPC ops to IPC as well
        commit: 148dd6a264900fe12c2b3d96efc40511dba177fc
[05/11] ASoC: SOF: control: Extend the optionality of IPC ops to IPC as well
        commit: cfa12c3679b49d8758b94c778afa6a71abf19989
[06/11] ASoC: SOF: sof-audio: Extend the optionality of IPC ops to IPC as well
        commit: cd6afb060c5a3cfad7582d5e09d43fd16a5202e5
[07/11] ASoC: SOF: topology: Extend the optionality of IPC ops to IPC as well
        commit: dbdbf88bdd4f29b391041ef887f89f7ae0809971
[08/11] ASoC: SOF: pm: Extend the optionality of IPC ops to IPC as well
        commit: 510758ee926a30b09b0692d1d42501847ab8b058
[09/11] ASoC: SOF: sof-priv: Mark fw_tracing ops optional in documentation
        commit: 1cf79c3484250d67180525662a247f8fecab3cea
[10/11] ASoC: SOF: trace: Use sof_ipc_get_ops() in sof_fw_trace_init
        commit: 8419fd90ee5c9038cb2776fad71fcc9b93f78e11
[11/11] ASoC: SOF: trace: No need to check for op pointer in sof_fw_trace_free()
        commit: 8a33863a0e287b17a5c637f231f31ff631348f8f

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