From: Curtis Malainey <cujomalainey@google.com>
To: Mark Brown <broonie@kernel.org>
Cc: Takashi Iwai <tiwai@suse.de>, Liam Girdwood <lgirdwood@gmail.com>,
Curtis Malainey <cujomalainey@chromium.org>,
ALSA development <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 08:23:21 -0800 [thread overview]
Message-ID: <CAOReqxj1V475mbfSEWNn3NrMJDttO+23KjboBR01tGhzAAJmBw@mail.gmail.com> (raw)
In-Reply-To: <20191128134901.GE4210@sirena.org.uk>
On Thu, Nov 28, 2019 at 5:49 AM Mark Brown <broonie@kernel.org> wrote:
>
> 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.
Sounds good, I will refactor this change and send a new version next
week as US is on holiday rest of this week.
_______________________________________________
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 16:24 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
2019-11-28 16:23 ` Curtis Malainey [this message]
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=CAOReqxj1V475mbfSEWNn3NrMJDttO+23KjboBR01tGhzAAJmBw@mail.gmail.com \
--to=cujomalainey@google.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).