mbox series

[0/4] ASoC: SOF: topology cleanups

Message ID 20231204214713.208951-1-pierre-louis.bossart@linux.intel.com (mailing list archive)
Headers show
Series ASoC: SOF: topology cleanups | expand

Message

Pierre-Louis Bossart Dec. 4, 2023, 9:47 p.m. UTC
Header alignment with firmware, addition of new token and partial
match filters.

Baofeng Tian (2):
  ASoC: SOF: align topology header file with sof topology header
  ASoC: SOF: add alignment for topology header file struct definition

Bard Liao (1):
  ASoC: SOF: topology: Use partial match for disconnecting DAI link and
    DAI widget

Curtis Malainey (1):
  ASoC: SOF: Wire up buffer flags

 include/sound/sof/topology.h    | 61 ++++++++++++++++++---------------
 include/uapi/sound/sof/tokens.h |  1 +
 sound/soc/sof/ipc3-topology.c   |  2 ++
 sound/soc/sof/topology.c        |  2 +-
 4 files changed, 38 insertions(+), 28 deletions(-)

Comments

Mark Brown Dec. 6, 2023, 2:23 p.m. UTC | #1
On Mon, 04 Dec 2023 15:47:09 -0600, Pierre-Louis Bossart wrote:
> Header alignment with firmware, addition of new token and partial
> match filters.
> 
> Baofeng Tian (2):
>   ASoC: SOF: align topology header file with sof topology header
>   ASoC: SOF: add alignment for topology header file struct definition
> 
> [...]

Applied to

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

Thanks!

[1/4] ASoC: SOF: topology: Use partial match for disconnecting DAI link and DAI widget
      commit: 2f03970198d6438d95b96f69041254bd39aafed0
[2/4] ASoC: SOF: align topology header file with sof topology header
      commit: 6c4df324d78ceb6a3ebb0d42243d131a424c85c3
[3/4] ASoC: SOF: add alignment for topology header file struct definition
      commit: 8ec56af3da4dad008ab10115eb4cec34836afc04
[4/4] ASoC: SOF: Wire up buffer flags
      commit: ebd12b2ca6145550a7e42cd2320870db02dd0f3c

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