Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: lgirdwood@gmail.com, Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
Cc: linux-sound@vger.kernel.org, kai.vehmanen@linux.intel.com,
	 ranjani.sridharan@linux.intel.com,
	yung-chuan.liao@linux.intel.com,  pierre-louis.bossart@linux.dev,
	liam.r.girdwood@intel.com,  cujomalainey@chromium.org,
	daniel.baluta@nxp.com, stable@vger.kernel.org
Subject: Re: [PATCH v2 0/2] ASoC: SOF: Correct sps->stream and cstream nullity management
Date: Thu, 06 Feb 2025 17:30:00 +0000	[thread overview]
Message-ID: <173886300019.325569.12850386648132801056.b4-ty@kernel.org> (raw)
In-Reply-To: <20241107134308.23844-1-peter.ujfalusi@linux.intel.com>

On Thu, 07 Nov 2024 15:43:06 +0200, Peter Ujfalusi wrote:
> Changes since v1:
> - Cc stable
> 
> The nullity of sps->cstream needs to be checked in sof_ipc_msg_data()
> and not assume that it is not NULL.
> The sps->stream must be cleared to NULL on close since this is used
> as a check to see if we have active PCM stream.
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: SOF: stream-ipc: Check for cstream nullity in sof_ipc_msg_data()
      commit: d8d99c3b5c485f339864aeaa29f76269cc0ea975
[2/2] ASoC: SOF: pcm: Clear the susbstream pointer to NULL on close
      commit: 46c7b901e2a03536df5a3cb40b3b26e2be505df6

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


  parent reply	other threads:[~2025-02-06 17:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-07 13:43 [PATCH v2 0/2] ASoC: SOF: Correct sps->stream and cstream nullity management Peter Ujfalusi
2024-11-07 13:43 ` [PATCH v2 1/2] ASoC: SOF: stream-ipc: Check for cstream nullity in sof_ipc_msg_data() Peter Ujfalusi
2024-11-08 13:34   ` Mark Brown
2024-11-07 13:43 ` [PATCH v2 2/2] ASoC: SOF: pcm: Clear the susbstream pointer to NULL on close Peter Ujfalusi
2025-02-06 17:30 ` Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-05 13:52 [PATCH v2 0/2] ASoC: SOF: Correct sps->stream and cstream nullity management Peter Ujfalusi
2025-02-06 17:30 ` Mark Brown

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=173886300019.325569.12850386648132801056.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=cujomalainey@chromium.org \
    --cc=daniel.baluta@nxp.com \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=lgirdwood@gmail.com \
    --cc=liam.r.girdwood@intel.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=pierre-louis.bossart@linux.dev \
    --cc=ranjani.sridharan@linux.intel.com \
    --cc=stable@vger.kernel.org \
    --cc=yung-chuan.liao@linux.intel.com \
    /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