mbox series

[0/4] ASoC: soc-dapm.c: random cleanup

Message ID 8735d59zt9.wl-kuninori.morimoto.gx@renesas.com
Headers show
Series ASoC: soc-dapm.c: random cleanup | expand

Message

Kuninori Morimoto Sept. 5, 2022, 11:17 p.m. UTC 
Hi Mark

These are cleanup patches for soc-dapm.c.
Each patches are not related, very random cleanup.

Kuninori Morimoto (4):
  ASoC: soc-dapm.c: don't use kzalloc() for param on snd_soc_dai_link_event_pre_pmu()
  ASoC: soc-dapm.c: don't use WARN_ON() at snd_soc_dai_link_event_pre_pmu()
  ASoC: soc-dapm.c: tidyup snd_soc_dai_link_event_pre_pmu()
  ASoC: soc-dapm.c: fixup snd_soc_dapm_new_control_unlocked() error handling

 sound/soc/soc-dapm.c | 77 +++++++++++++++++++-------------------------
 1 file changed, 33 insertions(+), 44 deletions(-)

Comments

Mark Brown Sept. 7, 2022, 1:37 p.m. UTC | #1 
On Mon, 5 Sep 2022 23:17:11 +0000, Kuninori Morimoto wrote:
> These are cleanup patches for soc-dapm.c.
> Each patches are not related, very random cleanup.
> 
> Kuninori Morimoto (4):
>   ASoC: soc-dapm.c: don't use kzalloc() for param on snd_soc_dai_link_event_pre_pmu()
>   ASoC: soc-dapm.c: don't use WARN_ON() at snd_soc_dai_link_event_pre_pmu()
>   ASoC: soc-dapm.c: tidyup snd_soc_dai_link_event_pre_pmu()
>   ASoC: soc-dapm.c: fixup snd_soc_dapm_new_control_unlocked() error handling
> 
> [...]

Applied to

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

Thanks!

[2/4] ASoC: soc-dapm.c: don't use WARN_ON() at snd_soc_dai_link_event_pre_pmu()
      commit: 427de091a7112aa8eaf2f689e95c0dbca5ea6543
[3/4] ASoC: soc-dapm.c: tidyup snd_soc_dai_link_event_pre_pmu()
      (no commit info)
[4/4] ASoC: soc-dapm.c: fixup snd_soc_dapm_new_control_unlocked() error handling
      commit: 3caac759681eeb31ac80e3cc14b972680c8bde54

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