Message ID | 87h6592qq3.wl-kuninori.morimoto.gx@renesas.com (mailing list archive) |
---|---|
Headers | show |
Series | ASoC: and adn use snd_soc_ret() | expand |
On Wed, 05 Feb 2025 00:13:40 +0000, Kuninori Morimoto wrote: > Each ASoC framwark is using own snd_xxx_ret() function, but we can share > these. This patch-set adds new snd_soc_ret() and use it. > > checkpatch indicates that ENOTSUPP is not a SUSV4 error code, prefer to > use EOPNOTSUPP. So this patch-set adds it, but not remove existing ENOTSUPP. > > Link: https://lore.kernel.org/r/8734gvsg5i.wl-kuninori.morimoto.gx@renesas.com > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/7] ASoC: add common snd_soc_ret() and use it commit: 943116ba2a6ab472e8ad2d1e57a3f10f13485cc2 [2/7] ASoC: soc-utils: care -EOPNOTSUPP on snd_soc_ret() commit: 062b7ef6b103dcbcb3c084e8ace8e74e260b2346 [3/7] ASoC: soc-pcm: use snd_soc_ret() commit: be61cd4242e4a53f5cf989ee7573121d041444bc [4/7] ASoC: simple-card: use snd_soc_ret() commit: a0ef5b4b101424b8a666ed56bf1717dafe2d37f5 [5/7] ASoC: simple-card-utils: use snd_soc_ret() commit: 2d7395b23dbf4c2d60be49b73e4c4705fc446662 [6/7] ASoC: audio-graph-card: use snd_soc_ret() commit: 74a0ca4c7f19f1b273d665b3b53f7ae8af879658 [7/7] ASoC: audio-graph-card2: use snd_soc_ret() commit: 8d83282e53185ec257a4ce08812e8fabee2c7212 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