[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <169833312844.133649.16742223419669591458.b4-ty@kernel.org>
Date: Thu, 26 Oct 2023 16:12:08 +0100
From: Mark Brown <broonie@...nel.org>
To: cezary.rojewski@...el.com, pierre-louis.bossart@...ux.intel.com,
liam.r.girdwood@...ux.intel.com, peter.ujfalusi@...ux.intel.com,
yung-chuan.liao@...ux.intel.com, ranjani.sridharan@...ux.intel.com,
kai.vehmanen@...ux.intel.com, perex@...ex.cz, tiwai@...e.com,
Su Hui <suhui@...china.com>
Cc: zhangyiqun@...tium.com.cn, amadeuszx.slawinski@...ux.intel.com,
alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
kernel-janitors@...r.kernel.org
Subject: Re: [PATCH] ASoC: Intel: Skylake: add an error code check in
skl_pcm_trigger
On Fri, 20 Oct 2023 17:26:20 +0800, Su Hui wrote:
> skl_decoupled_trigger() can return error code like -EPIPE if failed,
> add check for this.
>
>
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: Intel: Skylake: add an error code check in skl_pcm_trigger
commit: f5c7bc7a1fad4e1e8d3d29d71dd9f430a3350f42
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