public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>
Subject: [GIT PULL] ASoC fixes for v6.3-rc7
Date: Wed, 19 Apr 2023 21:24:11 +0100	[thread overview]
Message-ID: <20230419202424.DE8CEC433A0@smtp.kernel.org> (raw)

The following changes since commit e3720f92e0237921da537e47a0b24e27899203f8:

  ASoC: SOF: avoid a NULL dereference with unsupported widgets (2023-03-29 14:40:18 +0100)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git tags/asoc-fix-v6.3-rc7

for you to fetch changes up to 86a24e99c97234f87d9f70b528a691150e145197:

  ASoC: fsl_asrc_dma: fix potential null-ptr-deref (2023-04-19 13:42:56 +0100)

----------------------------------------------------------------
ASoC: Fixes for v6.3

A few remaining small fixes for v6.3, all small driver specific ones.

----------------------------------------------------------------
Chancel Liu (1):
      ASoC: fsl_sai: Fix pins setting for i.MX8QM platform

Daniel Baluta (1):
      ASoC: SOF: pm: Tear down pipelines only if DSP was active

Long Wang (1):
      ASoC: max98373: change power down sequence for smart amp

Nikita Zhandarovich (1):
      ASoC: fsl_asrc_dma: fix potential null-ptr-deref

Peter Ujfalusi (1):
      ASoC: SOF: ipc4-topology: Clarify bind failure caused by missing fw_module

 sound/soc/codecs/max98373.c   |  4 ++--
 sound/soc/fsl/fsl_asrc_dma.c  | 11 ++++++++---
 sound/soc/fsl/fsl_sai.c       |  2 +-
 sound/soc/sof/ipc4-topology.c | 10 ++++++----
 sound/soc/sof/pm.c            |  8 +++++++-
 5 files changed, 24 insertions(+), 11 deletions(-)

             reply	other threads:[~2023-04-19 20:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-19 20:24 Mark Brown [this message]
2023-04-20  5:14 ` [GIT PULL] ASoC fixes for v6.3-rc7 Takashi Iwai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230419202424.DE8CEC433A0@smtp.kernel.org \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=lgirdwood@gmail.com \
    --cc=tiwai@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox