linux-kernel - Re: [PATCH] ASoC: soc-core: skip zero num

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <164493110923.974741.6888113145562787379.b4-ty@kernel.org>
Date:   Tue, 15 Feb 2022 13:18:29 +0000
From:   Mark Brown <broonie@...nel.org>
To:     lgirdwood@...il.com, alsa-devel@...a-project.org, tiwai@...e.com,
        perex@...ex.cz, linux-kernel@...r.kernel.org,
        Shengjiu Wang <shengjiu.wang@....com>
Subject: Re: [PATCH] ASoC: soc-core: skip zero num_dai component in searching dai name

On Thu, 10 Feb 2022 19:19:12 +0800, Shengjiu Wang wrote:
> In the case like dmaengine which's not a dai but as a component, the
> num_dai is zero, dmaengine component has the same component_of_node
> as cpu dai, when cpu dai component is not ready, but dmaengine component
> is ready, try to get cpu dai name, the snd_soc_get_dai_name() return
> -EINVAL, not -EPROBE_DEFER, that cause below error:
> 
> asoc-simple-card <card name>: parse error -22
> asoc-simple-card: probe of <card name> failed with error -22
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: soc-core: skip zero num_dai component in searching dai name
      commit: f7d344a2bd5ec81fbd1ce76928fd059e57ec9bea

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