From: Mark Brown <broonie@kernel.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>
Subject: Re: [PATCH v2 0/4] ASoC: remove unnecessary dai_link->platform
Date: Fri, 24 Mar 2023 16:37:13 +0000 [thread overview]
Message-ID: <167967583379.2616375.6522996550461207982.b4-ty@kernel.org> (raw)
In-Reply-To: <87pm8zjd0t.wl-kuninori.morimoto.gx@renesas.com>
On Thu, 23 Mar 2023 22:53:12 +0000, Kuninori Morimoto wrote:
> Current ASoC will ignore already connected component when binding Card.
> This will happen mainly "CPU Component" is handled as "Platform Component",
> which was needed before.
>
> static int snd_soc_rtd_add_component(...)
> {
> ...
> for_each_rtd_components(rtd, i, comp) {
> /* already connected */
> if (comp == component)
> return 0;
> }
> ...
> }
>
> [...]
Applied to
broonie/sound.git for-next
Thanks!
[1/4] ASoC: fsl: remove unnecessary dai_link->platform
commit: 33683cbf49b5412061cb1e4c876063fdef86def4
[2/4] ASoC: atmel: remove unnecessary dai_link->platform
commit: 2f650f87c03cab72e751fc739f42a1e257bdc6b9
[3/4] ASoC: ti: remove unnecessary dai_link->platform
commit: 3b0db249cf8fe0027e2a4161d27a8566d82fcd80
[4/4] ASoC: soc-topology.c: remove unnecessary dai_link->platform
commit: e7098ba9b3785d626326040d300f95fec79aa765
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
prev parent reply other threads:[~2023-03-24 16:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 22:53 [PATCH v2 0/4] ASoC: remove unnecessary dai_link->platform Kuninori Morimoto
2023-03-23 22:53 ` [PATCH v2 1/4] ASoC: fsl: " Kuninori Morimoto
2023-03-23 22:53 ` [PATCH v2 2/4] ASoC: atmel: " Kuninori Morimoto
2023-03-23 22:53 ` [PATCH v2 3/4] ASoC: ti: " Kuninori Morimoto
2023-03-23 22:53 ` [PATCH v2 4/4] ASoC: soc-topology.c: " Kuninori Morimoto
2023-03-27 7:12 ` Péter Ujfalusi
2023-03-27 23:20 ` Kuninori Morimoto
2023-03-28 6:49 ` Péter Ujfalusi
2023-03-29 0:20 ` Kuninori Morimoto
2023-03-24 16:37 ` Mark Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=167967583379.2616375.6522996550461207982.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=kuninori.morimoto.gx@renesas.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.