From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Daniel Mack <daniel@caiaq.de>
Cc: alsa-devel@alsa-project.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Sven Neumann <s.neumann@raumfeld.com>,
Michael Hirsch <m.hirsch@raumfeld.com>
Subject: Re: [PATCH] ALSA: ASoC: move dma_data from snd_soc_dai to snd_soc_pcm_stream
Date: Fri, 19 Mar 2010 08:50:23 +0000 [thread overview]
Message-ID: <1268988623.3757.4.camel@odin> (raw)
In-Reply-To: <1268940238-6283-1-git-send-email-daniel@caiaq.de>
On Thu, 2010-03-18 at 20:23 +0100, Daniel Mack wrote:
> This fixes a memory corruption when ASoC devices are used in
> full-duplex mode. Specifically for pxa-ssp code, where this pointer
> is dynamically allocated for each direction and destroyed upon each
> stream start.
>
> All other platforms are fixed blindly, I couldn't even compile-test
> them. Sorry for any breakage I may have caused.
>
> Signed-off-by: Daniel Mack <daniel@caiaq.de>
> Cc: Liam Girdwood <lrg@slimlogic.co.uk>
> Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>
> Cc: Sven Neumann <s.neumann@raumfeld.com>
> Cc: Michael Hirsch <m.hirsch@raumfeld.com>
> Reported-by: Sven Neumann <s.neumann@raumfeld.com>
> Reported-by: Michael Hirsch <m.hirsch@raumfeld.com>
> ---
>
> I indeed missed quite a few platforms, you were right.
> Hope I got them all now. Better check again - thanks!
>
All the platforms here look fine.
Acked-by: Liam Girdwood <lrg@slimlogic.co.uk>
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
prev parent reply other threads:[~2010-03-19 8:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 16:17 Memory corruption in ASoC Daniel Mack
2010-03-18 16:43 ` Mark Brown
2010-03-18 16:48 ` Daniel Mack
2010-03-18 17:07 ` Mark Brown
2010-03-18 17:35 ` Liam Girdwood
2010-03-18 18:08 ` [PATCH] ALSA: ASoC: move dma_data from snd_soc_dai to snd_soc_pcm_stream Daniel Mack
2010-03-18 18:11 ` Daniel Mack
2010-03-18 18:22 ` Mark Brown
2010-03-18 18:28 ` Daniel Mack
2010-03-18 19:23 ` Daniel Mack
2010-03-19 6:56 ` Peter Ujfalusi
2010-03-19 7:08 ` Daniel Mack
2010-03-19 15:14 ` Mark Brown
2010-03-19 18:39 ` Daniel Mack
2010-03-19 19:54 ` Mark Brown
2010-03-20 14:54 ` Daniel Mack
2010-03-20 15:30 ` Mark Brown
2010-03-20 15:39 ` Daniel Mack
2010-03-20 16:14 ` Mark Brown
2010-03-22 9:10 ` Daniel Mack
2010-03-22 9:11 ` Daniel Mack
2010-04-01 17:18 ` Daniel Mack
2010-03-20 15:43 ` Daniel Mack
2010-03-19 9:14 ` Jarkko Nikula
2010-03-19 8:50 ` 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=1268988623.3757.4.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=daniel@caiaq.de \
--cc=m.hirsch@raumfeld.com \
--cc=s.neumann@raumfeld.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).