[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <168487140940.278276.10853655095714956345.b4-ty@kernel.org>
Date: Tue, 23 May 2023 20:50:09 +0100
From: Mark Brown <broonie@...nel.org>
To: 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>,
Rander Wang <rander.wang@...el.com>,
Jyri Sarha <jyri.sarha@...el.com>,
sound-open-firmware@...a-project.org, alsa-devel@...a-project.org,
linux-kernel@...r.kernel.org,
Harshit Mogalapalli <harshit.m.mogalapalli@...cle.com>
Cc: error27@...il.com, dan.carpenter@...aro.org,
kernel-janitors@...r.kernel.org
Subject: Re: [PATCH next] ASoC: SOF: Intel: hda-dai: Fix locking in
hda_ipc4_pre_trigger()
On Thu, 18 May 2023 23:44:01 -0700, Harshit Mogalapalli wrote:
> hda_ipc4_pre_trigger() has two issues:
> 1. In the default case, we are returning without unlocking the mutex.
> 2. In case SNDRV_PCM_TRIGGER_STOP: when ret is less than zero it goes
> to out, unlocks but returns zero instead of a negative value.
>
> Fix this by changing the final return value to 'ret' instead of zero,
> and initialize 'ret' to zero in the start of the function.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: SOF: Intel: hda-dai: Fix locking in hda_ipc4_pre_trigger()
commit: ed67a3404a8806a57c0015ce97bd3e6d61e7aa22
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