From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] ASoC: Use the correct DAPM context when cleaning up final widget set
Date: Wed, 09 Mar 2011 11:55:30 +0000 [thread overview]
Message-ID: <1299671730.3360.86.camel@odin> (raw)
In-Reply-To: <1299612689-770-1-git-send-email-broonie@opensource.wolfsonmicro.com>
On Tue, 2011-03-08 at 19:31 +0000, Mark Brown wrote:
> Now we've got multi-component we need to make sure that the DAPM context
> (and hence register I/O context) we use to apply the pending updates at
> the end of a DAPM sequence is the one we were processing rather than the
> one that was used to initate the state change.
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
> sound/soc/soc-dapm.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
Acked-by: Liam Girdwood <lrg@ti.com>
prev parent reply other threads:[~2011-03-09 11:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 19:31 [PATCH] ASoC: Use the correct DAPM context when cleaning up final widget set Mark Brown
2011-03-09 11:55 ` Liam Girdwood [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=1299671730.3360.86.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=patches@opensource.wolfsonmicro.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;
as well as URLs for NNTP newsgroup(s).