From: Mark Brown <broonie@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Curtis Malainey <cujomalainey@chromium.org>,
alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.com>
Subject: Re: [alsa-devel] [PATCH] ASoC: core: only flush inited work during free
Date: Thu, 28 Nov 2019 13:49:01 +0000 [thread overview]
Message-ID: <20191128134901.GE4210@sirena.org.uk> (raw)
In-Reply-To: <s5hlfs0ld25.wl-tiwai@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 387 bytes --]
On Thu, Nov 28, 2019 at 07:39:30AM +0100, Takashi Iwai wrote:
> For this delayed_work, the situation is a bit complex, though.
> Usually the work is set up to point to a fixed function, but in the
> case of ASoC, it seems serving for different purposes depending on the
> component type. I guess the cleaner way would be a redirect call
> like:
Yes, or just separate fields for each.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
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-11-28 13:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 1:13 [alsa-devel] [PATCH] ASoC: core: only flush inited work during free Curtis Malainey
2019-11-28 6:39 ` Takashi Iwai
2019-11-28 13:49 ` Mark Brown [this message]
2019-11-28 16:23 ` Curtis Malainey
2019-11-28 17:28 ` Mark Brown
2019-12-02 22:50 ` Curtis Malainey
2019-12-09 18:59 ` [alsa-devel] Applied "ASoC: core: only flush inited work during free" to the asoc tree Mark Brown
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=20191128134901.GE4210@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=cujomalainey@chromium.org \
--cc=lgirdwood@gmail.com \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
/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.