On Thu, 23 Jul 2020 20:38:57 +0200, Stephan Gerhold wrote: > At the moment we have two separate functions to parse the sound card > properties from the device tree: qcom_snd_parse_of() for DPCM and > apq8016_sbc_parse_of() without DPCM. These functions are almost identical > except for a few minor differences. > > This patch set extends qcom_snd_parse_of() to handle links without DPCM, > so that we can use one common function for all (qcom) machine drivers. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/7] ASoC: qcom: Use devm for resource management commit: ed3b53e7ffe91c32a1277de435e3fcb3ad5e852a [2/7] ASoC: qcom: common: Use snd_soc_dai_link_set_capabilities() commit: 627ab55d745b2a413e0a2856f2ad2e422a697971 [3/7] ASoC: q6afe: Remove unused q6afe_is_rx_port() function commit: 0a8c336a1e020be3832b02e1ddbb92d61da87512 [4/7] ASoC: qcom: common: Support parsing links without DPCM commit: 47ea88488209226e03559bb8baaa0156b4025fee [5/7] ASoC: qcom: common: Parse properties with "qcom," prefix commit: f0d67fdba5dcf48865fc79f2d63b49bd75d36671 [6/7] ASoC: qcom: apq8016_sbc: Use qcom_snd_parse_of() commit: 118205d241ef6fec395086c34f85717a41a8b4a1 [7/7] ASoC: qcom: common: Avoid printing errors for -EPROBE_DEFER commit: a63419beafd4edf20761c37dbefd639a0b1b481e 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
