[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <168362477289.305930.16081039230793204822.b4-ty@kernel.org>
Date: Tue, 09 May 2023 18:32:52 +0900
From: Mark Brown <broonie@...nel.org>
To: alsa-devel@...a-project.org,
V sujith kumar Reddy <Vsujithkumar.Reddy@....com>
Cc: Vijendar.Mukunda@....com, Basavaraj.Hiregoudar@....com,
Sunil-kumar.Dommati@....com, venkataprasad.potturu@....com,
ssabakar@....com,
Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
Liam Girdwood <lgirdwood@...il.com>,
Peter Ujfalusi <peter.ujfalusi@...ux.intel.com>,
Bard Liao <yung-chuan.liao@...ux.intel.com>,
Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>,
Kai Vehmanen <kai.vehmanen@...ux.intel.com>,
Daniel Baluta <daniel.baluta@....com>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>, Paul Olaru <paul.olaru@....com>,
Ajit Kumar Pandey <AjitKumar.Pandey@....com>,
"moderated list:SOUND - SOUND OPEN FIRMWARE (SOF) DRIVERS"
<sound-open-firmware@...a-project.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ASoC: SOF: amd: Fix NULL pointer crash in
acp_sof_ipc_msg_data function
On Mon, 08 May 2023 12:35:08 +0530, V sujith kumar Reddy wrote:
> Check substream and runtime variables before assigning.
>
>
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: SOF: amd: Fix NULL pointer crash in acp_sof_ipc_msg_data function
commit: 051d71e073614a72ad423d6dacba37a7eeff274d
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
Powered by blists - more mailing lists