From: Mark Brown <broonie@kernel.org>
To: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
Cc: lgirdwood@gmail.com, 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,
stable@vger.kernel.org, cujomalainey@chromium.org,
daniel.baluta@nxp.com
Subject: Re: [PATCH 2/2] ASoC: SOF: pcm: Clear the susbstream pointer to NULL on close
Date: Mon, 16 Dec 2024 12:30:41 +0000 [thread overview]
Message-ID: <fcba714e-7450-40b2-a681-81a214ac3c5d@sirena.org.uk> (raw)
In-Reply-To: <20241213131318.19481-3-peter.ujfalusi@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 211 bytes --]
On Fri, Dec 13, 2024 at 03:13:18PM +0200, Peter Ujfalusi wrote:
> Fixes: ef8ba9f79953 ("ASoC: SOF: Add support for compress API for stream data/offset")
> Cc: stable@vger.kernel.org
This commit doesn't exist.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-12-16 12:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 13:13 [PATCH 0/2] ASoC: SOF: Correct sps->stream and cstream nullity management Peter Ujfalusi
2024-12-13 13:13 ` [PATCH 1/2] ASoC: SOF: stream-ipc: Check for cstream nullity in sof_ipc_msg_data() Peter Ujfalusi
2024-12-16 12:30 ` Mark Brown
2024-12-13 13:13 ` [PATCH 2/2] ASoC: SOF: pcm: Clear the susbstream pointer to NULL on close Peter Ujfalusi
2024-12-16 12:30 ` Mark Brown [this message]
2025-02-06 17:30 ` [PATCH 0/2] ASoC: SOF: Correct sps->stream and cstream nullity management Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2024-11-07 13:39 Peter Ujfalusi
2024-11-07 13:39 ` [PATCH 2/2] ASoC: SOF: pcm: Clear the susbstream pointer to NULL on close Peter Ujfalusi
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=fcba714e-7450-40b2-a681-81a214ac3c5d@sirena.org.uk \
--to=broonie@kernel.org \
--cc=cujomalainey@chromium.org \
--cc=daniel.baluta@nxp.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.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