From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Bard liao <yung-chuan.liao@linux.intel.com>,
broonie@kernel.org, tiwai@suse.de
Cc: alsa-devel@alsa-project.org, kuninori.morimoto.gx@renesas.com,
bard.liao@intel.com
Subject: Re: [alsa-devel] [PATCH] ASoC: core: delete component->card_list in soc_remove_component only
Date: Tue, 17 Sep 2019 09:33:01 -0500 [thread overview]
Message-ID: <eb36ffa8-2d8c-6077-82f3-e8bb505399b7@linux.intel.com> (raw)
In-Reply-To: <20190916210353.6318-1-yung-chuan.liao@linux.intel.com>
On 9/16/19 4:03 PM, Bard liao wrote:
> From: Bard Liao <yung-chuan.liao@linux.intel.com>
>
> We add component->card_list in the end of soc_probe_component(). In
> other words, component->card_list will not be added if there is an
> error in the soc_probe_component() function. So we can't delete
> component->card_list in the error handling of soc_probe_component().
>
> Fixes: 22d1423187e5 ("ASoC: soc-core: add soc_cleanup_component()")
> Signed-off-by: Bard Liao <yung-chuan.liao@linux.intel.com>
Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
I wish we had a way to do this on the SOF GitHub, it's painful that
prior reviews and approvals are not tracked automagically.
> ---
> sound/soc/soc-core.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/sound/soc/soc-core.c b/sound/soc/soc-core.c
> index 35f48e9c5ead..aff4b4bf4d07 100644
> --- a/sound/soc/soc-core.c
> +++ b/sound/soc/soc-core.c
> @@ -978,7 +978,6 @@ static void soc_cleanup_component(struct snd_soc_component *component)
> /* For framework level robustness */
> snd_soc_component_set_jack(component, NULL, NULL);
>
> - list_del(&component->card_list);
> snd_soc_dapm_free(snd_soc_component_get_dapm(component));
> soc_cleanup_component_debugfs(component);
> component->card = NULL;
> @@ -991,7 +990,7 @@ static void soc_remove_component(struct snd_soc_component *component)
> return;
>
> snd_soc_component_remove(component);
> -
> + list_del(&component->card_list);
> soc_cleanup_component(component);
> }
>
>
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-09-17 14:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 21:03 [alsa-devel] [PATCH] ASoC: core: delete component->card_list in soc_remove_component only Bard liao
2019-09-17 14:33 ` Pierre-Louis Bossart [this message]
2019-09-17 16:02 ` [alsa-devel] Applied "ASoC: core: delete component->card_list in soc_remove_component only" to the asoc tree Mark Brown
2019-09-18 0:51 ` [alsa-devel] [PATCH] ASoC: core: delete component->card_list in soc_remove_component only Kuninori Morimoto
2019-09-18 2:47 ` Liao, Bard
2019-09-18 4:06 ` Kuninori Morimoto
2019-09-18 5:27 ` Liao, Bard
2019-09-18 5:46 ` Kuninori Morimoto
2019-09-18 6:13 ` Liao, Bard
2019-09-18 12:07 ` Mark Brown
2019-09-18 12:31 ` Liao, Bard
2019-09-18 12:53 ` Mark Brown
2019-09-18 23:50 ` Kuninori Morimoto
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=eb36ffa8-2d8c-6077-82f3-e8bb505399b7@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=broonie@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=tiwai@suse.de \
--cc=yung-chuan.liao@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox