[PATCH v3 0/2] ASoC: fix usage of playback_only and capture_only

Shengjiu Wang posted 2 patches 2 weeks, 5 days ago
sound/soc/fsl/imx-card.c              | 2 ++
sound/soc/generic/simple-card-utils.c | 4 ++--
2 files changed, 4 insertions(+), 2 deletions(-)
[PATCH v3 0/2] ASoC: fix usage of playback_only and capture_only
Posted by Shengjiu Wang 2 weeks, 5 days ago
Check value of is_playback_only and is_capture_only in
graph_util_parse_link_direction() and initialize playback_only and
capture_only in imx-card.c

changes in v3:
- initialize playback_only and capture_only for each loop in patch 2/2

changes in v2:
- check value of is_playback_only and is_capture_only
- add patch 2/2 to initialize playback_only and capture_only

Shengjiu Wang (2):
  ASoC: simple-card-utils: Check value of is_playback_only and
    is_capture_only
  ASoC: fsl: imx-card: initialize playback_only and capture_only

 sound/soc/fsl/imx-card.c              | 2 ++
 sound/soc/generic/simple-card-utils.c | 4 ++--
 2 files changed, 4 insertions(+), 2 deletions(-)

-- 
2.34.1
Re: [PATCH v3 0/2] ASoC: fix usage of playback_only and capture_only
Posted by Mark Brown 2 weeks, 5 days ago
On Wed, 18 Mar 2026 18:28:48 +0800, Shengjiu Wang wrote:
> ASoC: fix usage of playback_only and capture_only
> 
> Check value of is_playback_only and is_capture_only in
> graph_util_parse_link_direction() and initialize playback_only and
> capture_only in imx-card.c
> 
> changes in v3:
> - initialize playback_only and capture_only for each loop in patch 2/2
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-7.0

Thanks!

[1/2] ASoC: simple-card-utils: Check value of is_playback_only and is_capture_only
      https://git.kernel.org/broonie/sound/c/0e9fc79132ce
[2/2] ASoC: fsl: imx-card: initialize playback_only and capture_only
      https://git.kernel.org/broonie/sound/c/ca67bd564e94

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