Message ID | 20230920153621.711373-1-chancel.liu@nxp.com (mailing list archive) |
---|---|
Headers | show |
Series | ASoC: soc-pcm.c: Make sure DAI parameters cleared if the DAI becomes inactive | expand |
On Wed, Sep 20, 2023 at 11:36:20PM +0800, Chancel Liu wrote: > It's reasonable that DAI parameters should be cleared if current DAI becomes > inactive. > > Only check DAI active status in soc_pcm_hw_free() is not enough since there's > the risk that DAI parameters never be cleared if there're more than one stream > [see A]. Only check DAI active status in soc_pcm_close() is also not enough > since it will cause the cleanup just happening in soc_pcm_close() [see B]. Please don't send cover letters for single patches, if there is anything that needs saying put it in the changelog of the patch or after the --- if it's administrative stuff. This reduces mail volume and ensures that any important information is recorded in the changelog rather than being lost.
On Wed, 20 Sep 2023 23:36:20 +0800, Chancel Liu wrote: > It's reasonable that DAI parameters should be cleared if current DAI becomes > inactive. > > Only check DAI active status in soc_pcm_hw_free() is not enough since there's > the risk that DAI parameters never be cleared if there're more than one stream > [see A]. Only check DAI active status in soc_pcm_close() is also not enough > since it will cause the cleanup just happening in soc_pcm_close() [see B]. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/1] ASoC: soc-pcm.c: Make sure DAI parameters cleared if the DAI becomes inactive commit: 3efcb471f871cc095841d411f98c593228ecbac6 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