mbox series

[v2,0/2] ASoC: SOF: add no_reply IPC calls

Message ID 20230419194057.42205-1-pierre-louis.bossart@linux.intel.com
Headers show
Series ASoC: SOF: add no_reply IPC calls | expand

Message

Pierre-Louis Bossart April 19, 2023, 7:40 p.m. UTC 
Simplify IPC messages to avoid passing a reply structure that is not
used later.

Changes since v1: fixed rebase issue leading to allmodconfig
compilation error

Curtis Malainey (2):
  ASoC: SOF: ipc: Add no reply inline calls
  ASoC: SOF: Use no_reply calls for TX

 sound/soc/sof/compress.c                  |  8 ++----
 sound/soc/sof/intel/hda-loader.c          |  2 +-
 sound/soc/sof/ipc3-dtrace.c               | 12 +++------
 sound/soc/sof/ipc3-pcm.c                  |  6 ++---
 sound/soc/sof/ipc3-topology.c             | 33 +++++++----------------
 sound/soc/sof/ipc3.c                      | 12 +++------
 sound/soc/sof/ipc4-pcm.c                  |  6 ++---
 sound/soc/sof/ipc4-topology.c             | 10 +++----
 sound/soc/sof/sof-client-ipc-flood-test.c |  3 +--
 sound/soc/sof/sof-client-probes-ipc3.c    | 12 +++------
 sound/soc/sof/sof-client-probes-ipc4.c    |  4 +--
 sound/soc/sof/sof-client.h                |  4 +++
 sound/soc/sof/sof-priv.h                  | 10 +++++++
 13 files changed, 51 insertions(+), 71 deletions(-)

Comments

Mark Brown April 21, 2023, 4:06 p.m. UTC | #1 
On Wed, 19 Apr 2023 14:40:55 -0500, Pierre-Louis Bossart wrote:
> Simplify IPC messages to avoid passing a reply structure that is not
> used later.
> 
> Changes since v1: fixed rebase issue leading to allmodconfig
> compilation error
> 
> Curtis Malainey (2):
>   ASoC: SOF: ipc: Add no reply inline calls
>   ASoC: SOF: Use no_reply calls for TX
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: SOF: ipc: Add no reply inline calls
      commit: ccb541a00b5bf87f1b7b9301373bf88a3257c688
[2/2] ASoC: SOF: Use no_reply calls for TX
      commit: 367fd6ffa294ca3346902aa0814fac31bb5a6059

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