From: Liam Girdwood <lrg@ti.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@kernel.org" <stable@kernel.org>
Subject: Re: [PATCH] ASoC: snd_soc_new_{mixer, mux, pga} make sure to use right DAPM context
Date: Thu, 9 Jun 2011 14:56:57 +0100 [thread overview]
Message-ID: <4DF0D129.8030301@ti.com> (raw)
In-Reply-To: <1307618556-32068-1-git-send-email-lars@metafoo.de>
On 09/06/11 12:22, Lars-Peter Clausen wrote:
> Currently it is possible that snd_soc_new_{mixer,mux,pga} is called with a
> DAPM context not matching the widgets context. This can lead to a wrong
> prefix_len calculation, which will result in undefined behaviour. To avoid
> this always use the DAPM context from the widget itself.
>
> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
> Cc: stable@kernel.org
>
Acked-by: Liam Girdwood <lrg@ti.com>
WARNING: multiple messages have this Message-ID (diff)
From: Liam Girdwood <lrg@ti.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@kernel.org" <stable@kernel.org>
Subject: Re: [PATCH] ASoC: snd_soc_new_{mixer,mux,pga} make sure to use right DAPM context
Date: Thu, 9 Jun 2011 14:56:57 +0100 [thread overview]
Message-ID: <4DF0D129.8030301@ti.com> (raw)
In-Reply-To: <1307618556-32068-1-git-send-email-lars@metafoo.de>
On 09/06/11 12:22, Lars-Peter Clausen wrote:
> Currently it is possible that snd_soc_new_{mixer,mux,pga} is called with a
> DAPM context not matching the widgets context. This can lead to a wrong
> prefix_len calculation, which will result in undefined behaviour. To avoid
> this always use the DAPM context from the widget itself.
>
> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
> Cc: stable@kernel.org
>
Acked-by: Liam Girdwood <lrg@ti.com>
next prev parent reply other threads:[~2011-06-09 13:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 11:22 [PATCH] ASoC: snd_soc_new_{mixer, mux, pga} make sure to use right DAPM context Lars-Peter Clausen
2011-06-09 11:22 ` [PATCH] ASoC: snd_soc_new_{mixer,mux,pga} " Lars-Peter Clausen
2011-06-09 13:56 ` Liam Girdwood [this message]
2011-06-09 13:56 ` Liam Girdwood
2011-06-09 14:08 ` [PATCH] ASoC: snd_soc_new_{mixer, mux, pga} " Mark Brown
2011-06-09 14:08 ` [PATCH] ASoC: snd_soc_new_{mixer,mux,pga} " 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=4DF0D129.8030301@ti.com \
--to=lrg@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
/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.