From: Mark Brown <broonie@kernel.org>
To: Cezary Rojewski <cezary.rojewski@intel.com>, alsa-devel@alsa-project.org
Cc: hdegoede@redhat.com, amadeuszx.slawinski@linux.intel.com,
pierre-louis.bossart@linux.intel.com, tiwai@suse.com
Subject: Re: [RESEND PATCH] ASoC: core: Exit all links before removing their components
Date: Sun, 20 Nov 2022 11:56:45 +0000 [thread overview]
Message-ID: <166894540585.1075876.9923695190281693260.b4-ty@kernel.org> (raw)
In-Reply-To: <20221027085840.1562698-1-cezary.rojewski@intel.com>
On Thu, 27 Oct 2022 10:58:40 +0200, Cezary Rojewski wrote:
> Flows leading to link->init() and link->exit() are not symmetric.
> Currently the relevant part of card probe sequence goes as:
>
> for_each_card_rtds(card, rtd)
> for_each_rtd_components(rtd, i, component)
> component->probe()
> for_each_card_rtds(card, rtd)
> for_each_rtd_dais(rtd, i, dai)
> dai->probe()
> for_each_card_rtds(card, rtd)
> rtd->init()
>
> [...]
Applied to
broonie/sound.git for-next
Thanks!
[1/1] ASoC: core: Exit all links before removing their components
commit: c7eb967d70446971413061effca3226578cb4dab
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:[~2022-11-20 11:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 8:58 [RESEND PATCH] ASoC: core: Exit all links before removing their components Cezary Rojewski
2022-11-18 10:56 ` Cezary Rojewski
2022-11-20 11:56 ` 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=166894540585.1075876.9923695190281693260.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=cezary.rojewski@intel.com \
--cc=hdegoede@redhat.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.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.